Apache Subversion

Best software for versioning of files or documents

Comentarios: Easy to use this software.
I would like to highlight some of its features in short note as following.
Create Repository, Checkout, Update, Perform Changes, Review Changes, Fix Mistakes, Resolve Conflicts,Commit Changes and many more.
After all these about features i would like to say that there should be one feature in it and that is while we are working on any file and meanwhile if any other is trying to edit that file then it should alert that someone else is working in this file. It will be help the both person that who is working on this file so they can work in that way which will reduce the conflicts of files.

Puntos a favor:

easy to maintain the current and historical versions of files such as source code, web pages, and documentations.

Puntos en contra:

according to my experience, there is no any features that i don't like about this software.

Subversion: Code storage another way.

Comentarios: Having come from Visual Source Safe in the early 2000s, Subversion was great in that it enabled more than one person to access and edit a file. Committing and merging those files is pretty straightforward and the flexibility it offers it good.
In addition, if there are secure areas of a project that only a few should see, the granular access features enable that to happen.

Puntos a favor:

Ease of use and having the master (centralised) copy on site. Subversion maintains a master copy - the main source - and copies are made from that. Also having the ability to properly store binary, rather than textual files, is a bonus when wanting to version images or PDFs. Like GIT, but not Visual Source Safe (when we migrated), SVN gives the ability for many people to edit and change files and to merge the changes.

Puntos en contra:

It is more difficult, if using an 'internal' server, to access remotely. You have to ensure that SSH tunnels etc are in place to grant remote access.

Managing Code Changes

Puntos a favor:

When I update a file, I just use "svn commit" to save the changes, and if needed, I can revert back easily with "svn revert". It's simple and keeps my workflow smooth.

Puntos en contra:

Unlike Git, it doesn't handle distributed workflows as smoothly. Also, its branching and merging features are not as advanced, making it more challenging for complex projects.

Version control

Comentarios: I've been using SVN ever since I've migrated from Microsoft VSS and I still find it as powerful as ever and still relevant in 2022. We now use much better visual tools and online hosting services integrated with testing and CI/CD tools but the core SVN experience is still as good as it was

Puntos a favor:

Personally I consider SVN to be the perfect balance between functionality and control. When working in a mixed team environment repository security and locking are paramount and SVN makes everything simple. Post commit hooks are also very useful and easy to implement.

Puntos en contra:

I like the git ability to perform local commits and I'd love to have it in SVN but it I find the benefits of a centralised repository much more important.

I Only Use It to Upload to a Public repository

Comentarios: I've been using Apache Subversion for almost a year, but not as my main version control software. Work on my projects using another version control software, then when projects are ready to ship to the public repository I simply paste in the folder of the latest version into my Subversion folder, so I don't use it for version control per se. I just use Subversion because the public repository I upload to uses it. That said, there's nothing outright bad about Subversion. Other version control software fits better into my normal build workflow.

Puntos a favor:

It works well for version control, and I am yet to have any merge conflicts. It allows users to determine the version numbers using built-in features. Version numbering is not straight forward, at least in my case. I only manage one application which needs to have the version number updated in 3 separate files, which is not quite straightforward at first. The public repository is much more easier to navigate and download software than the private version

Puntos en contra:

It's not as easy to use as other version control software. With Apache Subversion it feels like I am manually creating files and then adding version tags or metadata to them, Whereas with my preferred version control system, I select which files I'm tracking, and whenever I need I commit the files to create new versions without having to manually separate the different versions.