Op Friday 26 March 2010 21:34 schreef u:
> Toma has noted that he won't be available to draft the 4.5 schedule. This is 
> something that needs to get done. Here's a draft based on the 4.3 schedule to 
> get us started with:

Thanks for that excellent work. I've changed the schedule a bit to reflect the 
following:

This cycle we saw that a beta1 and hard feature freeze at the same date was not 
optimal. People committing features last minute made packaging beta 1 a 
nightmare. I've now set the hard feature freeze 1 week before tagging.

This cycle we experimented a bit with a message freeze where typo fixes were 
allowed. I've no made it part of the release schedule by introducing a soft 
message freeze and a hard message freeze. See techbase page for details. 

We also experimented with releasing rc's asap after tagging. This went pretty 
well, though innocent looking commits broke the tarballs. To prevent that, i've 
introduced a tagging freeze. This means 24h before tagging no commits other 
than build fixes should be committed. All other commits are not allowed 
(including showstoppers). Showstoppers should go through reviewboard, so we can 
determine if it is indeed a showstopper and if it is safe to commit in relation 
to all platforms we support.

Final problem we had this cycle was changing dependencies until late in the 
schedule. I want to stop that insanity. So I added a dependency freeze at the 
soft feature freeze time. People should by then know what they want to add as 
features for that cycle and think about the dependencies they need. During the 
dependency freeze it is not allowed to introduce new dependencies or raise the 
version of existing dependencies.

I hope you agree to these changes so we can make the schedule final soonish.
http://techbase.kde.org/Schedules/KDE4/4.5_Release_Schedule

Best,

Toma
-- 
KDE Developer
_______________________________________________
release-team mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/release-team

Reply via email to