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

Re: Subversion 1.5 Release decision?

From: Mark Phippard <markphip_at_gmail.com>
Date: Thu, 22 May 2008 18:29:24 -0400

On Thu, May 22, 2008 at 4:38 PM, Karl Fogel <kfogel_at_red-bean.com> wrote:
> "Hyrum K. Wright" <hyrum_wright_at_mail.utexas.edu> writes:
>> Huh? We've *always* released from the tip of the 1.y.x branch.
>> Releasing from something other than that seems like it would involve a
>> bit more process than we currently use, but maybe the new features
>> make that possible now. Personally, I'd rather not mess with
>> additional release branches; if we don't want to include stuff that's
>> already been merged, let's just back it out, cut the tarball, and then
>> remerge it (and pray mergetracking works as advertised).
> Specifically, what I was thinking was:
> Make a branch based on the 1.5.0-rc5 tag, then port over to that branch
> all the changes we want: the ones approved in 1.5.x since RC5 was
> released that we also consider conservative/trivial enough to go into
> 1.5.0 without a full resoak.
> That list has been floated in several forms in this thread already. I
> think any of us could come up with it pretty quickly; let me know if you
> want me to do it.

Are you against reverse merging and putting the items back in STATUS?
It seems to work and is far easier if we only want to exclude a
handful of the revisions (which I think is the case).

Mark Phippard
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-05-23 00:29:42 CEST

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.