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

Changing the CHANGES file

From: <pll_at_lanminds.com>
Date: 2003-07-24 17:08:50 CEST


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

Any strong opinions either way?


Key fingerprint = 1660 FECC 5D21 D286 F853  E808 BB07 9239 53F1 28EE
	It may look like I'm just sitting here doing nothing,
   but I'm really actively waiting for all my problems to go away.
	 If you're not having fun, you're not doing it right!
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:09:48 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.