[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: rev 5085 - branches

From: Greg Stein <gstein_at_lyra.org>
Date: 2003-02-27 02:56:33 CET

On Mon, Feb 24, 2003 at 10:51:53PM -0500, Michael Price wrote:
> mprice@tigris.org writes:
> > Author: mprice
> > Date: 2003-02-24 21:26:24 -0600 (Mon, 24 Feb 2003)
> > New Revision: 5085
> >
> > Added:
> > branches/release-0.18.1/
> > Log:
> >
> > Create the 0.18.1 release branch from the 0.18 release.
> >
> > Copied: release-0.18.1 (from rev 5084, tags/0.18)
>
> So, which bogus revision number am I putting in the changes file this
> time?

I don't think you need to put a "bogus" number in there. You just need to
specify the *path* that was used. For example, see the 0.17.0 section in
CHANGES:

   Version 0.17.0 (released 20 Jan 2003, branches/0.17 @ revision 4468)

Thus, you would go ahead and use the youngest revision, but in conjunction
with the path, you're specifying the exact code used for the release.

All that said, I think Karl's suggestion is now making sense. We probably
ought to just start calling our releases subversion-0.18.1.tar.gz or
somesuch, rather than using revision numbers in there.

Cheers,
-g

p.s. yes, I realize all of this is post-release, but still want to mention
it to the list...

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 27 02:52:06 2003

This is an archived mail posted to the Subversion Dev mailing list.