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

Re: Changing the CHANGES file

From: David Summers <david_at_summersoft.fay.ar.us>
Date: 2003-07-24 17:05:59 CEST

On Thu, 24 Jul 2003 pll@lanminds.com wrote:
> I've received some feedback from the announcement of the 0.26
> release, which is tied to the format of the CHANGES file.
> Specifically, the concern is with the first line
> which mentions "branches/release-0.26.0".
> The confusion was over the fact that 'branches/release-0.26.0' really
> looks like a named branch point, yet, once a release is made, this is
> moved to a tag, which isn't mentioned anywhere. As a result, we're
> advertising something which technically doesn't exist, and that which
> does exist is getting no mention at all.
> As more people come to Subversion, more people (such as those
> exclusively on the users@ list) will be tracking the project by the
> announcements made to the lists, and the news posted on the website,
> both of which include the latest portion of the CHANGES file and
> mention this now non-existent release branch.
> It seems to me that we might rather mention the tag area, since
> that's what will exist once a release is finallized. Does this make
> sense?
> Any strong opinions either way?

I agree. My RPM release versions have been .... confusing .... if looked
at from the viewpoint of the CHANGES file because sometimes I've been able
to use the revision number mentioned in the CHANGES file and sometimes

It would be nice to have them match and have it be the tag revision
number if possible.

Also it is conusing to *later* try to go back to a previous release and
not easily be able to do "svn log" and other commands from the
release branch (because it no longer exists in HEAD).

David Wayne Summers          "Linux: Because reboots are for hardware upgrades!"
david_at_summersoft.fay.ar.us   PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint =  C0 E0 4F 50 DD A9 B6 2B  60 A1 31 7E D2 28 6D A8 
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 24 17:26:25 2003

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.