Re: KDE SC 4.6 Schedule
On Sat May 29 2010 14:15:49 Albert Astals Cid wrote: Thanks, I've put the schedule online now. Found a little error, Soft Message Freeze says Typo fixes can be fixed until Beta2, but Hard Message Freeze does not kick in until 12 days after Beta2, can we change the text of Soft Message Freeze to say Typo fixes can be fixed until Hard Message Freeze? I'm not much of a translator (not at all, in fact), but aren't typos restricted to one language? And would the translated version still work (but be fuzzy)? If those assumptions are true (translations aren't broken by fixing a typo, but only marked as have another look), then I'd propose to just allow typo fixes, whenever. If not, please educate me :D -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE SC 4.6 Schedule
A Diumenge, 30 de maig de 2010, Sebastian Kügler va escriure: On Sat May 29 2010 14:15:49 Albert Astals Cid wrote: Thanks, I've put the schedule online now. Found a little error, Soft Message Freeze says Typo fixes can be fixed until Beta2, but Hard Message Freeze does not kick in until 12 days after Beta2, can we change the text of Soft Message Freeze to say Typo fixes can be fixed until Hard Message Freeze? I'm not much of a translator (not at all, in fact), but aren't typos restricted to one language? And would the translated version still work (but be fuzzy)? If those assumptions are true (translations aren't broken by fixing a typo, but only marked as have another look), then I'd propose to just allow typo fixes, whenever. If not, please educate me :D fuzzy effectively means untranslated, so no your suggestion is not valid. Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE SC 4.6 Schedule
[Albert Astals Cid - Sonntag 30 Mai 2010 11:04:59] A Diumenge, 30 de maig de 2010, Sebastian Kügler va escriure: On Sat May 29 2010 14:15:49 Albert Astals Cid wrote: Thanks, I've put the schedule online now. Found a little error, Soft Message Freeze says Typo fixes can be fixed until Beta2, but Hard Message Freeze does not kick in until 12 days after Beta2, can we change the text of Soft Message Freeze to say Typo fixes can be fixed until Hard Message Freeze? I'm not much of a translator (not at all, in fact), but aren't typos restricted to one language? And would the translated version still work (but be fuzzy)? If those assumptions are true (translations aren't broken by fixing a typo, but only marked as have another look), then I'd propose to just allow typo fixes, whenever. If not, please educate me :D fuzzy effectively means untranslated, so no your suggestion is not valid. ...and to add some explanation. :) Changes to the original string has to mark the translated string fuzzy because gettext cannot see if you just fixed a typo or something that changed the meaning. Furthermore a typo fix can change how a translater understands and translates the string. So after a typo fix, all translators have to check the string and unfuzz it for it being shown in the UI again. Regards ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE SC 4.6 Schedule
On Sun May 30 2010 11:43:06 Frederik Schwarzer wrote: [Albert Astals Cid - Sonntag 30 Mai 2010 11:04:59] A Diumenge, 30 de maig de 2010, Sebastian Kügler va escriure: On Sat May 29 2010 14:15:49 Albert Astals Cid wrote: Thanks, I've put the schedule online now. Found a little error, Soft Message Freeze says Typo fixes can be fixed until Beta2, but Hard Message Freeze does not kick in until 12 days after Beta2, can we change the text of Soft Message Freeze to say Typo fixes can be fixed until Hard Message Freeze? I'm not much of a translator (not at all, in fact), but aren't typos restricted to one language? And would the translated version still work (but be fuzzy)? If those assumptions are true (translations aren't broken by fixing a typo, but only marked as have another look), then I'd propose to just allow typo fixes, whenever. If not, please educate me :D fuzzy effectively means untranslated, so no your suggestion is not valid. ...and to add some explanation. :) Changes to the original string has to mark the translated string fuzzy because gettext cannot see if you just fixed a typo or something that changed the meaning. Furthermore a typo fix can change how a translater understands and translates the string. So after a typo fix, all translators have to check the string and unfuzz it for it being shown in the UI again. Ok, thanks for the explanation! :-) -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE SC 4.6 Schedule
A Dijous, 27 de maig de 2010, Tom Albers va escriure: On Wed, 26 May 2010 22:00:38 +0100, Albert Astals Cid aa...@kde.org wrote: I like it. Albert Thanks, I've put the schedule online now. Found a little error, Soft Message Freeze says Typo fixes can be fixed until Beta2, but Hard Message Freeze does not kick in until 12 days after Beta2, can we change the text of Soft Message Freeze to say Typo fixes can be fixed until Hard Message Freeze? Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE SC 4.6 Schedule
On Wed, 26 May 2010 22:00:38 +0100, Albert Astals Cid aa...@kde.org wrote: I like it. Albert Thanks, I've put the schedule online now. -- Tom Albers KDE Developer ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE SC 4.6 Schedule
A Divendres, 21 de maig de 2010, Tom Albers va escriure: On Fri, 21 May 2010 12:41:54 +0200, Will Stephenson wstephen...@kde.org 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
KDE SC 4.6 Schedule
With my distribution hat on I'm wondering when KDE SC 4.6 will come out. Aiming for our traditional end of January release, we would have a 5 1/2 month cycle, which is appreciably shorter than what we have achieved during the last 2 releases due to slippages. However if it is released later, it wanders into the time period when distributions would be wanting to freeze their package version numbers for their spring releases. I know it's early but I'd like to do some long range risk planning that might affect 4.6's release, and come up with a schedule promptly after 4.5. Factors off the top of my head with my risk assessment: * Qt releases - 4.7 should be well out and stable then. LOW * Camp KDE - will probably happen around this time, but doesn't have a significant hacking component. LOW * Sprints - is there anything big like a Tokamak in preparation for January? I assume there will be an Osnabrueck KDEPIM meeting but I hope that will be generating 4.7 work and PIM's focus in the 4.6 cycle will be on consolidation after the 4.5 'tick' to Akonadi. MEDIM * Development programs: I'm not aware of any dev programs like GSoC that will be delivering around that time. LOW Will ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE SC 4.6 Schedule
On Fri, 21 May 2010 12:41:54 +0200, Will Stephenson wstephen...@kde.org 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
