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

Re: 1.5 stabilization procedure

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2007-10-17 09:48:58 CEST

On 10/17/07, Stefan.Fuhrmann@etas.de <Stefan.Fuhrmann@etas.de> wrote:
> Hi TSVN contributors!
> Since the Subversion guys will branch 1.5.x Really Soon Now (TM),
> I was wondering how and when we will follow. My understanding is
> that TSVN used to branch shortly after SVN.

There weren't that many major releases yet, so we haven't really come
to a point where we can tell we 'usually' do something specific :)

> For the log and rev graph stuff, I plan to finish the feature work
> packages
> in the next 2 weeks. Therefore, I would like to ask for a branch target
> date no earlier than October, 31th. Later, if SVN should not have branched
> by that date. Is that acceptable?
> So far I don't know of any document that states the merging policy
> for TSVN stabilization and maintenance branches. So, I like to ask the
> following questions:
> * Who selects patches that shall go from /trunk into
> /branches/1.5.x?
> * How do we track them?
> * Who will merge them?
> * When will they be merged?
> * Is there some kind of review or other QA for those patches?


Basically, our rules are:
* each developer decides himself whether a patch should get backported
to the stable branch
* there's a file "STATUS.txt" in the release branch were each
backported revision is noted.
  but with svn 1.5 and merge tracking, we don't really need that one anymore.
* the dev who committed the fix to trunk does usually also the merging
* they're merged as soon as possible
* Not really. I kick the nightly build after somethings got committed
to the stable branch, which will then make available a new, fresh
nightly build from the stable branch.

> I don't mean to start bikeshed discussions here. It's just that we should
> document what we do (or give me a pointer to a place where this has
> already been done).

About creating the stable branch:
I suggest we wait a while before we create the stable branch. Because
once svn creates the stable branch, there's still a lot of work to do
to get all API calls up to date and make use of all new features. I
would even recommend that we create our stable branch at most a week
before subversion creates the tag.
And maybe I even roll out an RC for TSVN before hitting the final 1.5...


  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Oct 17 09:49:04 2007

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

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