Change release schedule 4.2 and schedule for 4.3

[Jordi Polo]

At this point of development I do prefer keep 4.2 scheduled as originally
planned or if needed make it longer, never make it shorter. Everyone has
their own preferences but at this point I am sure some projects (akonadi
above for instance) have very much already planned for the original 4.2
schedule.

I think making 4.3  5 months or 9 months release is wiser (I'd advocate for
5m to try not to screw up the 6m cycle) .

we need a feature freeze period for schedules changes :P

As for the Qt/KDE alignment, with 6months/9months releases cycles , aren't
we able to use Qt trunk at least half of the releases ?


On Mon, Sep 8, 2008 at 2:15 AM, Thiago Macieira <thiago at kde.org> wrote:

> Tom Albers wrote:
> >> Also note that Qt has a 8-10 month release schedule.
> >
> >Again, if there is any real advantage lineing up with that schedule,
> > please come to the release-team mailinglist and convince us.
>
> Quite frankly, there are a lot of advantages. For example, given the
> current schedule, KDE 4.2 code cannot use Qt 4.5 snapshots or pre-final
> releases. It cannot make use of any of the performance improvements we're
> making, nor try out the new features for animation.
>
> Given the current branching policy in KDE, trunk will be frozen at the end
> of this month and will be unfrozen when 4.2 branches, sometime around
> December.
>
> That means the critical period for reviews is entirely missed.
>
> Of course, that's a moot discussion for 4.2: I would not advocate
> extending it by 3 months. But it's something to think about for future,
> especially since 4.3 seems like the perfect opportunity.
>
> --
>   Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
>     PGP/GPG: 0x6EF45358; fingerprint:
>     E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
>



-- 
Jordi Polo Carres
NLP laboratory - NAIST
http://www.bahasara.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20080908/7a6b6da2/attachment.htm>