[Kde-pim] Re: Do we need a Beta3?

[Tom Albers]

----- Original Message -----
> The current schedule calls for the next tagging on 21 Dec to be a
> Release Candidate.

If you want to insert an extra beta, i like to keep the usual interval for beta's. That way the schedule from now on would be like this:

=== Monday, December 13, 2010: Documentatin Freeze ===
No more substantive changes to documentation or handbooks after this date. Typos, spelling and simple grammar changes are permitted.

=== Thursday, December 16, 2010: Beta 3 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 22, 2010: Beta 3 Release ===
The beta becomes available for general consumption.

=== Monday, January 3, 2011: 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, January 3, 2011: 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, January 3, 2011: 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 to contact kde-i18n-doc for every single string change, if noone objects in 5 days you can commit the change.

=== Monday, January 3, 2011: 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, January 4, 2011: Release Candidate 1 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 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 17, 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 18, 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 19, 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, February 2, 2011: Final Tag ===
The branch is frozen for final release tagging. Only urgent fixes, such as those fixing compilation errors, should be committed. 

=== Wednesday, February 9, 2011: Release ===
Final release is released for general consumption.

(Please use playground/utils/releaseschedule if you want to play more)

Best,
-- 
Tom Albers
KDE Release Team
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/