From kde-release-team Wed May 26 21:00:38 2010 From: Albert Astals Cid Date: Wed, 26 May 2010 21:00:38 +0000 To: kde-release-team Subject: Re: KDE SC 4.6 Schedule Message-Id: <201005262200.39007.aacid () kde ! org> X-MARC-Message: https://marc.info/?l=kde-release-team&m=127490769404187 A Divendres, 21 de maig de 2010, Tom Albers va escriure: > On Fri, 21 May 2010 12:41:54 +0200, Will Stephenson > > wrote: > > With my distribution hat on I'm wondering when KDE SC 4.6 will come out. > > Hi Will, > > If we aim for the end of january, I suggest the schedule below. In > trunk/playground/utils/releaseschedule I've just committed an application > which can help us create this schedule automatically. If anyone wants to > play with different freeze times, feel free, it has loads of settings to > fiddle with. Beta testers also welcome :) > > Proposed 4.6.0 schedule as generated by this application: > > Thursday, October 28, 2010 - Soft Feature Freeze > Trunk is frozen for feature commits that are not listed in the planned > feature document. Only bugfixes and the code implementing the listed > features are to be committed after this date. The feature list also closes > today. > > Features not already finished or not listed on the planned features page > will have to wait until the next KDE SC release. > > Thursday, November 11, 2010 - Soft Message Freeze > All translated messages (GUI strings) are frozen on this date. Only > previously untranslated strings or clear errors in strings can be fixed. No > major new strings changes should be done. It is ok to remove strings. > Exception: Artwork (try to keep the number of new strings low anyways). > Exception: Typo fixes can be fixed until Beta2 is released but you have to > mail kde-i18n-doc saying you made a typo fix change. > > Thursday, November 11, 2010 - Soft API Freeze > To allow the bindings people to have proper time to do their work in > preparation to the final release, the API should now be mostly fixed. > Changing API is allowed, but commits have to be cc'ed to the kde-bindings > mailinglist. This is including older APIs and newly introduced > libraries/APIs. > > Thursday, November 11, 2010 - Dependency Freeze > From this moment on it is not allowed to add new dependencies or bump > dependencies versions. It is possible to get an exception for this. Post > the patch to reviewboard and add the release-team as reviewer. We will > check if the dependency is needed and is available on all platforms. > > In other words: If you have a feature that requires a new dependency or a > version of a dependency that is higher than currently checked for in the > build system, you need to have committed this change before this date. > > Thursday, November 11, 2010 - Hard Feature Freeze > Trunk is frozen for all feature commits, even those listed in the planned > feature document. Only bug fixes are allowed. > > Thursday, November 18, 2010 - Beta 1 Tagging > Trunk is frozen for beta release tagging. Only urgent fixes, such as those > fixing compilation errors, should be committed. The usual beta rules apply > as soon as the Beta tarballs have been generated. > > Wednesday, November 24, 2010 - Beta 1 Release > The beta becomes available for general consumption. > > Monday, November 29, 2010 - Documentatin Freeze > No more substantive changes to documentation or handbooks after this date. > Typos, spelling and simple grammar changes are permitted. > > Thursday, December 2, 2010 - Beta 2 Tagging > Trunk is frozen for beta release tagging. Only urgent fixes, such as those > fixing compilation errors, should be committed. The usual beta rules apply > as soon as the Beta tarballs have been generated. > > Wednesday, December 8, 2010 - Beta 2 Release > The beta becomes available for general consumption. > > Monday, December 20, 2010 - Tagging Freeze for Release Candidate 1 > During tagging freeze only compilation fixes for all platforms are allowed > to be committed. Everything else (even showstopper fixes) *have* to be run > through reviewboard, with the release-team and the affected maintainers as > reviewer. > > Monday, December 20, 2010 - Hard API Freeze > To allow the bindings people to have proper time to do there work in > preparation to the final release, the API is now frozen. No more changes to > APIs or header files (except docs) after this date, including older APIs > and newly introduced libraries/APIs. > > Monday, December 20, 2010 - Hard Message Freeze > Up to now you were able to do typo changes, but you had to mail > kde-i18n-doc saying you made a typo fix change. From this moment on you > need an explicit ok beforehand from kde-i18n-doc for every single string > change. > > Monday, December 20, 2010 - Artwork and Bindings Freeze > All artwork is frozen on this date. No new artwork should be added. > Existing artwork can continue to be tweaked and fixed. > > No new additions to the language bindings, except optional bindings as > permitting by the kde-bindings team. > > Tuesday, December 21, 2010 - Release Candidate 1 Tagging > Trunk is frozen for release candidate tagging. Only urgent fixes, such as > those fixing compilation errors, should be committed. > > Wednesday, December 22, 2010 - Release Candidate 1 Release > The release candidate is tagged from the branch. Only urgent fixes, such > as those fixing compilation errors, should be committed.As soon as the RC > has been confirmed to build it will be released immediately. > > Monday, January 3, 2011 - Tagging Freeze for Release Candidate 2 > During tagging freeze only compilation fixes for all platforms are allowed > to be committed. Everything else (even showstopper fixes) *have* to be run > through reviewboard, with the release-team and the affected maintainers as > reviewer. > > Tuesday, January 4, 2011 - Release Candidate 2 Tagging > Trunk is frozen for release candidate tagging. Only urgent fixes, such as > those fixing compilation errors, should be committed. > > Wednesday, January 5, 2011 - Release Candidate 2 Release > The release candidate is tagged from the branch. Only urgent fixes, such > as those fixing compilation errors, should be committed.As soon as the RC > has been confirmed to build it will be released immediately. > > Wednesday, January 19, 2011 - Final Tag > The branch is frozen for final release tagging. Only urgent fixes, such as > those fixing compilation errors, should be committed. > > Wednesday, January 26, 2011 - Release > Final release is released for general consumption. I like it. Albert _______________________________________________ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team