Svn changes version from one number to major.minor

Question

I am trying to change svn version number due to getting major.minor.release format. In my configuration, the svn version number is incremented by 1 for each commit. Could it be changed?

I am learning how to do this using perl, but for me it would be gold if you could offer some kind of ace in solving holes.

Answer 1

It is not possible that you may need to flag specific versions that match your releases.

Answer 2

Do not use mix version numbers and release numbers. Just don't abuse it that way.

The very last thing, when you switch RCS, say, git subversion, you are screwed. Seriously do your versioning manually. In the best case, include the revision number for subversion as an indicator of postfix construction.

What do you get from linking release version numbers to internal RCS numbering? These numbers are essentially unique identifiers for the system, not software version numbers. They are fixation numbers , so don't mess with this.

Answer 3

No, you cannot change the version number of SVN , and you should not either.

Under the hood, SVN makes a (lazy) copy of the entire repository tree every time you check something. This copy is saved and accessed by identifier, and this identifier is called the revision number . This is a piece of information inside your repository , and with the exception of the need to refer to a specific revision, the value of this identifier should not bother you.

What version number is your software bundle delivered to customers is what you decided externally from the repository and regardless of the number of checks in the repository. (Your customers don't care if you need a hundred checks to implement brilliant new features and smooth out those nasty bugs or a thousand of them.)

It is your task as a developer to establish a connection between the internal revision number and the number of versions used . This is done by tagging (or branching if you plan to have several small releases from this major version). If there is a specific revision that you want to publish as version 1.0, just copy that revision to something like tags/releases/1.0 . (Note that this even allows you to mix source files from different versions for one version. Just selectively update them to specific versions and when you have the state in which you want to mark this mixed working copy.)

The SVN book explains all this. Do yourself a favor and walk a few hours to read it. It will pay off in a few days.