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

Re: Issue 791 (repair timestamps of uhchanged files)

From: Simon Large <slarge_at_blazepoint.co.uk>
Date: 2005-02-01 14:27:50 CET

Max Bowsher wrote:
> Simon Large wrote:
>> Or am I just misunderstanding the release procedure?
> The latter. Nothing has to be proposed for 1.2, as trunk *is* 1.2.

Does that mean that HACKING is incorrect?

Stabilizing and maintaining releases

Minor and major number releases go through a stabilization period
before release, and remain in maintenance (bugfix) mode after release.
To start the release process, we create an "A.B.x" branch based on the
previous release, for example:

   $ svn cp http://svn.collab.net/repos/svn/tags/A.(B-1).C \


As I read it it suggests that 1.2.0 will be taken from tags/1.1.3 (which
sounds unmanageable). From what you have said, that pattern applies only
to minor (3rd digit increment) releases, with major release branches
being copied from trunk.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 1 14:29:44 2005

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.