[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-release-team
Subject:    Re: 4.2 Schedule.
From:       Allen Winter <winter () kde ! org>
Date:       2008-07-16 15:20:40
Message-ID: 200807161120.41309.winter () kde ! org
[Download RAW message or body]

On Wednesday 16 July 2008 10:33:45 Sebastian Kügler wrote:
> On Wednesday 16 July 2008 15:12:07 Allen Winter wrote:
> > On Monday 16 June 2008 12:12:08 Tom Albers wrote:
> > I noticed that today's RC1 announcement mentions that 4.2 is expected in
> > January. So we should probably publish the 4.2 schedule on TechBase
> > soonish.
> 
> Agree.
> 
> > I think we should keep the same schedule from 4.1,
> > except time-shifted forward 6months, like so:
> >
> > Sun 19 Oct: Soft Feature Freeze
> > Tue 21 Oct: Tag Alpha1
> > Tue 28 Oct: Release Alpha2
> > Tue 18 Nov: Message Freeze
> > Tue 18 Nov: Tag Beta1
> > Tue 25 Nov: Release Beta1
> > Tue  9 Dec: Tag Beta2
> > Tue 16 Dec: Release Beta2
> > Tue  6 Jan: Tag RC1
> > Tue 13 Jan: Release RC1
> > Tue 20 Jan: Tag 4.2
> > Tue 27 Jan: Release 4.2
> 
> It does not take into account Toma's proposal of shorter freeze periods, but 
> that can maybe be taken care of as we move to a  more distributed development 
> model ("always summer in trunk").
> 
Personally, I liked the "rhythm" of 4.1.  It felt right to me.
Of course, I wasn't really developing any new features at all -- simply trying
to get kdepim into a working state.

Please explain how "always summer in trunk" would work.

> When do we hard-freeze? (Around beta2 looks sensible to me...)
> 
The hard feature freeze would occur on beta1.
At least, that's what we did for 4.1.
I think we need to stop features at the first beta.

> Otherwise, I'm all for finalising the 4.2 schedule quickly.
_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

[prev in list] [next in list] [prev in thread] [next in thread]