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

Re: Backporting to issue-2489 branch

From: Karl Fogel <kfogel_at_red-bean.com>
Date: Tue, 19 Aug 2008 15:12:40 -0400

Senthil Kumaran S <senthil_at_collab.net> writes:
> I would like to backport r32550 and future work if any from trunk to
> issue-2489 branch, is there any procedure I need to follow in order to
> do that? ie., should I get approval from committers before I do the
> backport? Please clarify me on this so that I can backport fixes to
> this branch in future. Also do we need to update the CHANGES file? or
> should we maintain a STATUS file in this branch?

I'm fine with a general policy of you being able to port trunk changes
over to the '1.5.x-issue2489' branch just so you can work. I'm not sure
we need a more general policy than that.

It would be very helpful for there to be a README.branch file on the
branch; +1 in advance on committing one :-). As we make user-visible
and developer-visible changes, we could update CHANGES on the branch, or
do it on trunk when we port the branch over. I don't think it matters
much either way.

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-08-19 21:12:55 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.