[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.Fuhrmann_at_etas.de>
Date: 2007-10-22 02:59:29 CEST

"Stefan Küng" <tortoisesvn@gmail.com> wrote on 17.10.2007 09:48:58:

> > 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
> > date no earlier than October, 31th. Later, if SVN should not have
> > 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?
> http://tortoisesvn.tigris.org/release_faq.html

Thanks for the pointers!

> 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

An SVN 1.5 repository server would be helpful. Also, the changes HTML
files for the stable branch should still contain at least the same
information as today.

> * 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
> > 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.

Maybe we should decide upon the branch date depending on TSVN's
stability at that time. One to Two weeks should be fine.

> And maybe I even roll out an RC for TSVN before hitting the final 1.5...

+1. This is the first mayor release after more than one year and
there was a lot of code churn. Therefore, users should definitely
be given time to do some testing. In combination with the Xmas /
New Year holiday season, testing will take some time but "release
pressure" will be less severe ...

-- Stefan^2.

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Oct 22 02:59:37 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.