Branko $,1 ,(Bibej writes:
> >or somesuch. This is possible now thanks to Philip's 'svnversion'
> >program, which see.
> >
> So are you suggesting we run svnversion as part of the build process? If
> so, I invite you to hack that yourself, instead of fobbing it off on an
> unsuspecting RM volunteer. :-)
:)
> >What do you think? This would mean that dist.sh, and possibly a few
> >other things, would need some tweaks, but it will make things a lot
> >clearer in the long run. Up for it?
>
> Can we please, please stop fooling around with this? Let's just admit
> that our labelling strategy is less than perfect, and just leave it at
> that.Or we can just document that the revision number in the version tag
> always comes off the release branch, not the trunk -- end of problem.
For this release my opinion is that we document that the revision number
in the version tag always comes off the release branch. After the
release we can come to a consensus on the desired behavior and I can
hack it up along with my fixes to the release "documentation".
Michael Price Member of the Engineering Staff
Distributed Processing Lab; Lockheed Martin Adv. Tech. Labs
A&E 3W; 1 Federal Street; Camden, NJ 08102
856-338-4021, fax 856-338-4144 email: mprice@atl.lmco.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 19 20:47:55 2003