Guideline from the train gang
J. Along with a UI freeze (or heavy slush) at M6 we should make sure all major features are at least
functional by M6. In other words, it would add risk to the quality of the release if anything big landed after M6.
M7 as always is feature freeze. We should only be bug fixing after that while ramping down towards a high quality delivery by early June.
Doug
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx]
On Behalf Of David M Williams
Sent: Monday, February 07, 2011 9:05 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Indigo Simultaneous Release Train : which milestone for UI freeze ?
There is a sections that discusses UI Freeze:
Support Translations. All strings must be externalized, and Projects must participate in Babel, meaning it is registered and available for string translation, etc. Projects must freeze the UI sufficiently early to allow the Babel project time to translate
strings so there can be simultaneous release of translated versions. The UI should be frozen by M6 (a "freeze" all major changes and additions are done by M6, and changes after that are done in a controlled, well documented fashion, so Babel translators can
more easily "keep up" with late changes).
It was written (intentionally) with a "must" part and a "should" part; "Projects
must freeze the UI sufficiently early to allow the Babel project time to translate strings so there can be simultaneous release of translated versions." and "The UI
should be frozen by M6". I think we ended up there, being a little ambiguous, because each project has a little different meaning or approach to "freeze" ... some mean it pretty absolute,
completely done, some mean it "mostly done, changes after that are limited, and controlled, and well documented".
Hopefully that's enough guidance to support both translation and documentation efforts. Above all, that's one reason for projects to define their own deadlines and processes in their rampdown plan,
so for anyone who is very sensitive to a projects policies can find out the policies and deadlines and plan their own work accordingly.
HTH
Thanks,
From: fgiquel@xxxxxxxxxxxxxxxx
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 02/07/2011 08:47 AM
Subject: [cross-project-issues-dev] Indigo Simultaneous Release Train : which milestone for UI freeze
?
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
Hi,
there is something which is not obvious to me about UI freeze deadline.
The page (http://eclipse.org/indigo/planning/EclipseSimultaneousRelease.php)
describes the API freeze as required for M6 but it does not talk about UI freeze.
I have seen on some Project plans M7 marked as "feature freeze" or "UI freeze".
Could someone tell if there are some requirement on "UI freeze" for M6 ?
Thanks,
Fabien Giquel_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
