Another RC?, was: Re: Akonadi-Nepomuk Feeder Improvements

Martin Gräßlin mgraesslin at kde.org
Mon Dec 31 15:44:18 UTC 2012


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?
> 
> Scott K
> _______________________________________________
> release-team mailing list
> release-team at kde.org
> https://mail.kde.org/mailman/listinfo/release-team
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/release-team/attachments/20121231/dc6edec2/attachment.sig>


More information about the release-team mailing list