+1 -Stepan.
On 11/25/07, Tim Ellison <[EMAIL PROTECTED]> wrote: > So if we agree on producing M4 on Fri Dec 14th, then working back from > that date we have: > > Code freeze on Fri Dec 7th. Feature freeze on Fri Nov 30th . > > So this coming week is the last chance to consider any new features or > major areas of functionality for inclusion in this milestone. > > After Fri 30 Nov our focus is on bug fixing, testing, and stabilizing > the code ready for the milestone. > > After Fri Dec 7th the code is frozen, meaning we are all testing and > discussing must-fix bugs that have a serious impact on declaring the > milestone. Defining a bug as "must-fix" requires (at least) two > committers during the freeze period (of course, everyone's opinion is > encouraged). We aim that this period is no more than a week, but we > will move the date if necessary to achieve the required quality. > > i.e., business as usual <g> > > Regards, > Tim > > Spark Shen wrote: > > Agree. > > > > 2007/11/23, Tim Ellison <[EMAIL PROTECTED]>: > >> I think we should agree a date to release our fourth stable milestone > >> build. There have been lots of good fixes and enhancements made > >> throughout the code, and while we have been doing well at maintaining > >> stability in 'head', I believe that many users wait for a declared > >> milestone before moving up. > >> > >> I propose that we aim for declaring M4 on Friday Dec 14th. That is > >> three weeks from today. > >> > >> That date gives us some buffer to overrun if we need it before the > >> holiday period gets into full swing. Once get near the end of December > >> and start of January there are many people taking a well-earned break, > >> and it will be harder to close out a release. > >> > >> To get in practice for an official release, I suggest we also try to > >> complete the full set of rel eng tasks, like release notes, download > >> signing, and announcements that we haven't been so good at in the past. > >> > >> What do you think? > >> Tim > >>
