I only have one release. Due to my laziness it's 1.0.0.136. I would
now like to create a tag 1.0.0.136 in the repository that reflects the
release running on the customers machine. If I tag now, the tags name
(identifying the version number) would not correspond with the
repositories revision number (which currently is 86).
All parts of the version number have predefined meanings. In short:
1.0.0.136
| | | |_ the repositories revision number
| | |____ bugfix number
| |______ minor number
|________ major number
-------------------------
Felix
Christopher Ness wrote:
CN> On Fri, 2005-06-17 at 15:33 +0200, Felix Brack wrote:
>> Hello Scott,
>>
>> Well, it's just a one time problem: we delivered a software to our
>> customer with version 1.0.0.136 (it's in the printed documents of the
>> software). The last part of the version number (136) is always the
>> revision number of the repository at the point the software is
>> released, i.e. I create a tag 1.0.0.136 in the repository at revision
>> 136. This is the way it normally should work.
>>
>> The problem is (as I said, a one time problem) that I did not put the
>> software under subversion control, at the beginning of the development
>> (no time for setup, first project for subversion control, there are
>> many (or better no) excuses for this silly mistake).
>>
>> Ok. The software was ready and I needed a version number. I called the
>> first release 1.0.0.136 with the idea of leaving some 'space' for other
CN> Try calling version two 1.0.1.86 ???
CN> Or does the 3rd vision number also have special meaning?
CN> Cheers,
CN> Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 17 16:52:06 2005