Component Leads: I'd like to propose
something similar to PMC at 11/16 meeting, unless there is objections from
any one due to complications I'm not aware of.
Please review quickly and let me know
if you foresee any problems (Sorry, I know that's only one day notice,
but I don't think there's too much room for controversy,
and M2 (12/22) is coming up fast!).
The main way's it impacts you will be
need to be plan to be "code complete" for planned M2 content
need to update milestone plans, if appropriate, to accurately reflect M2
content by 12/10.
need to plan to provide test plan for M2 by 12/10
need to plan to execute that test plan from 12/10 to 12/22, fixing sev
1 and some sev 2 problems (with an upgrade to Eclipse M4 "at the last
The one issue that's "sticky"
is that I believe there will be code in the build that is not in
the M2 milestone plan, per se (e.g. Snippets View, Web Services, etc.).
Ideally, to avoid confusion on what
community should look at, open bugs against, etc., this function would
be "off" in final builds (by renaming plugins to plugin.xml.off?)
but perhaps easier to just document
what's in and what's not? To be concrete, I'll propose former (truly off)
to see if someone has strong opinion or a better idea.
According the WebTools charter, "The
PMC is responsible for establishing the level of testing appropriate for
each Project, and approving the test plans ".
While a bit vague, it does seem to indicate
that "testing" is an appropriate PMC topic, so ... I suggest
the following "high level" plan for discussion/approval at PMC
Ultimately, I'm assuming the main goal
is to have a overall "test plan" for the *release* .... but presumably
the main part of that would be to "test each milestone". So,
this "proposed plan" is just to cover the next milestone. I should
bring up now to be sure we are all "on the same page".
Overall, I've tried to plan in an extended
period of testing for this milestone, due to the tight timing with Eclipse
base milestone, and the fact that many will be taking vacations
during this holiday period of time.
That is, its not so much there will be extra testing .... but will best
be planned to be done a little earlier than usual, so the "final test"
can be a brief regression. And, there's not much time left!, relatively
- candidate build for M2 (on Eclipse M3), component
test plans complete, component teams (and community) begins "milestone
12/20 (Friday) - upgrade build for
final candidate build (include Eclipse M4, and "most recent"
versions of pre-req projects).
12/20 to 12/22, "regression tests"
with new base/pre-reqs.
12/22 (Wednesday) milestone M2 declared
During this "milestone shutdown" period 12/10
to 12/22), the goal is to fix all "sev 1" problems, "most
sev 2", and for components to not introduce anything new, so as to
not risk last minute regressions. This means all function proposed for
the milestone must be complete by 12/10, and any other work, done for following
milestone, should not be released to build. This should give time between
now and 12/10 for component leads to update milestone plan to be more specific
about what's in and what's out of M2 milestone (and update following milestones).