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

Re: Let's set a date/goal for the 1.5 Branch

From: Mark Phippard <markphip_at_gmail.com>
Date: 2007-09-01 01:45:43 CEST

On 8/31/07, Hyrum K. Wright <hyrum_wright@mail.utexas.edu> wrote:

> Daniel Rall wrote:
> > On Fri, 31 Aug 2007, Mark Phippard wrote:
> > ...
> >> 3. I am assuming is fairly stable already, known issues not with
> >> standing. I would hope we would branch and cut RC1 all in a short
> >> time frame. At least that is what I proposing.
> >
> > This is what I groked from Mark's original message -- get ready to cut
> > an RC by mid-October (which implies a branch). If we have a lot messy
> > outstanding issues remaining at this time, there's no point in cutting
> > an RC, and thus no point in branching (due to porting overhead,
> > testing benefits, etc.).
> >
> > So, as Greg said, the issue list defines the RC point. And as Mark
> > suggested, let's shoot to knock all the issues off that list by
> > mid-October.
>
> As part of this process, it would be good to cull the 1.5-consider herd,
> and either move stuff postpone it to 1.6 (preferable) or move it to 1.5.
> Not that I'm volunteering, just something more that should be done.

Well if we did not already put them in the list, odds are this is not
the best time, but we can always see where things stand in a couple of
weeks in terms of progress. I suspect there are several items
currently in the 1.5 milestone we will want to postpone, rather than
adding new stuff.

Certainly at some point we need to change those milestones though, so yes.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Sep 1 01:42:49 2007

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.