Re: Re[4]: Setting head revision number

On Fri, 2005-06-17 at 16:50 +0200, Felix Brack wrote:
> 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).

Tags are much more powerful than revision numbers. Therefore I don't
use revision numbers in my tag names.

I prefer not to expose internal development revision numbers for just
this reason. There is another thread that just finished up discussing
revision numbers and reasons why not to depend on them (even in CVS!)

      Unclear: CVS and Subversion repository difference.

> 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

Gaining (or syncing with) revision control would be a good bug fix I
think. ;)

But it's a management decision. You could always pad your repository
with useless commits to get to the right version number. But that seems
silly to me.

Good luck,
Chris

-- 
Wireless Group,
McMaster University
finger.localdomain
11:00:38 up 1 day, 19:24, 2 users, load average: 0.00, 0.01, 0.03
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org