Time based releases?

[Leonardo Franchi]

On Friday 27 March 2009 09:54:33 Mark Kretschmann wrote:
> On Fri, Mar 27, 2009 at 10:49 AM, Lydia Pintscher <lydia at kde.org> wrote:
> > On Fri, Mar 27, 2009 at 10:31, Nikolaj Hald Nielsen
> >
> > <nhnfreespirit at gmail.com> wrote:
> >>> I think the idea of a concrete release cycle is good---it gives us
> >>> focus and allows us to work hard on new features then switch to bugfix
> >>> mode. But I don't see why we need to fix the release cycle for *all*
> >>> our releases beforehand--- why not just decide the length of the next
> >>> release cycle after each release? Most likely we'll have more
> >>> information at hand, and can tailor it to our specific needs.
> >>
> >> +1
> >>
> >> But it might make sense to set a date for next release, feature freeze
> >> and so on as soon as the previous release is out. That will give
> >> everyone a better idea of how much tie there really is to add big new
> >> features. Meaning that as soon as 2.1.0 is out, we set dates for 2.1.1
> >> ( and possibly even for 2.2.0 ). That makes sense to me, but going
> >> beyond that does not.
> >
> > +1
>
> +1 -1
>
> (I thought the "me2" became unfashionable years ago.)

great, i think we're now actually all saying the same thing. so we'll discuss  
2.1.1 and 2.2 plans after 2.1 is released. or at the sprint. that probably 
works way better.

leo

-- 
-----
lfranchi at kde.org		Tufts  University 2010
leonardo.franchi at tufts.edu                The KDE Project