Rockbox mail archive
Subject: Re: Release schedule proposal
Re: Release schedule proposal
2008/11/5 Dave Chapman <dave_at_dchapman.com>:
> There's just been a brief discussion in IRC suggesting that we create a
> strict timetable for releases as follows:
> * Releases happen every 3 months, with the date of 3.0 (23rd September)
> being the reference point, so releases would be:
> 23 March
> 23 June
> 23 September
> 23 December
> * Feature freeze would happen two weeks before release (i.e. the 9th), and
> the creation of the release branch would happen one week before release
> (i.e. the 16th).
> Any opinions/objections?
I'm not against the idea, but I wonder what the point of releasing so
often is unless there was something big?
On your time line you have freeze, branch, release. What about tracker
cleanup, manual fixes, mad rush to get ready patches in?
I think we should either release every 4 months instead of 3 to give a
bit more gap to do each one properly, or do similar to the ubuntu
"schedule" where one release is a bugfix/stable one and the next is
more about features (bug fixes still go in of course....)
I'm not suggesting adding every patch in the tracker which is in
sync... I'm just trying to shrink the number of open patches. What I'm
suggesting is that we do a call out onto the mailing lists saying if
people have patches they want in and are willing to get them up to
scratch then we are more open to have them committed. Doing this every
release will probably be bad which is why I'm suggesting every second
Last thing... I wonder if 2 days before xmas is going to be workable?
won't most people have more important IRL things to do?
(P.S yes I think there are a fair amount of good patches on the
tracker which just need syncing to be acceptable, and I may very well
be in the minority here....)
Received on 2008-11-05
Page was last modified "Jan 10 2012" The Rockbox Crew