KDE 4.10 release schedule changes, was: We are having RC3 was: Re: Another RC?, was: Re: Akonadi-Nepomuk Feeder Improvements
ubuntu at kitterman.com
Mon Dec 31 21:23:48 UTC 2012
Since KDE SC 4.10.0 is now the day before Alpha 2 is planned, it would make
sense to me to ask to have it moved a week later.
---------- Forwarded Message ----------
Subject: We are having RC3 was: Re: Another RC?, was: Re: Akonadi-Nepomuk
Date: Monday, December 31, 2012, 05:23:11 PM
From: Albert Astals Cid <aacid at kde.org>
To: release-team at kde.org, Christian Mollekopf <chrigi_1 at fastmail.fm>, Vishesh
Handa <me at vhanda.in>
El Dilluns, 31 de desembre de 2012, a les 16:44:18, Martin Gräßlin va
> On Sunday 30 December 2012 20:55:22 Scott Kitterman wrote:
> > On Monday, December 31, 2012 12:24:18 AM Sebastian Kügler wrote:
> > > On Sunday, December 30, 2012 02:41:43 Scott Kitterman wrote:
> > > > Assuming 4.10.1 and 4.10.2 slip similarly, that would result in the
> > > > next
> > > > Kubuntu release having 4.10.1 instead of 4.10.2. We might also have
> > > > to
> > > > make some adjustments to our internal testing milestone schedule.
> > > >
> > > > 4.10.2 would come out a day or two before Kubuntu 13.04 (far to late
> > > > for
> > > > pre- release updates) so we'd get to release without the current KDE
> > > > SC. We do ship the point releases as post-release updates, so they
> > > > would
> > > > get to users eventually, but post-release QA is a lot more work for
> > > > us.
> > > >
> > > > This isn't precisely a problem, but changing the release cycle now is
> > > > not
> > > > idea for us. As long as 4.11 drops back into the usual time slot
> > > > (and
> > > > doesn't also slip), then the impact would not be major.
> > >
> > > Would adding in two instead of three weeks work for you?
> > No. Looking at the schedule, it would need to be only a week later than
> > the current schedule to make it. If the 4.10.0 -> 4.10.1 and 4.10.1 ->
> > 4.10.2 intervals were slightly reduced, maybe we could get there?
> what about Kubuntu uses stable from branch as of freeze day? That would be
> very close to 4.10.2.
> Or maybe tag 4.10.2 at the Kubuntu freeze day, but otherwise keep the
> schedule shifted?
Honestly, who cares if Kubuntu ships 4.10.1(because we made an RC3) or 4.10.2
(because we did not make an RC3)?
It will still be "x days" after the freeze so the code quality will be very
Since it seems almost everyone agrees we want an RC3 but noone is doing the
step to announce it, i will do it.
We will keep the same separation as between RC1 and RC2, i.e. two weeks, so
January 2, 2013: KDE SC 4.10 Tagging Freeze for Release Candidate 2
January 3, 2013: KDE SC 4.10 Release Candidate 2 Tagging
January 4, 2013: KDE SC 4.10 Release Candidate 2 Release
January 16, 2013: KDE SC 4.10 Tagging Freeze for Release Candidate 3
January 17, 2013: KDE SC 4.10 Release Candidate 3 Tagging
January 18, 2013: KDE SC 4.10 Release Candidate 3 Release
January 30, 2013: KDE SC 4.10 Final Tag
February 6, 2013: KDE SC 4.10 Release
Vishesh, Christian can you please commit your respective code ASAP?
More information about the kubuntu-devel