[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [eclipse.org-planning-council] Staging the next iteration
|
Hi Dave,
assuming that there might be USB sticks again to hold next
year's
coordingate release at EclipseCon, it's probably not even
sure whether
M5 is early enough.
But even not considering the sticks, I think it's wiser to
plan for M5
be "The EclipseCon milestone" and avoid unnecessary rush.
Having
the milestone available long enough before EclipseCon will
allow for
critical fixes to go into an M5prime if needed, and it will
allow for
Tutorial slides etc. to be prepared on base of M5, such
that the
slides and presentations are in sync with the actual
milestone.
I guess that individual projects who want to show off some
late breaking
new features could always do so based on their own
project's downloads,
but for the train I'm almost certain that planning M5 to be
"the EclipseCon
release" is wiser.
Thanks for bringing that up now anyways, since this does
allow us
to consider the things in time.
Cheers,
--
Martin Oberhuber, Senior Member of Technical
Staff, Wind River
Target Management Project
Lead, DSDP PMC Member
I don't know what the best
solution is, but one problem I've spotted with this schedule is the
March 13th M6 date.
That does not give enough time for
"the train" to have a milestone before EclipseCon (23rd)
Ideally, M6 +0 would be one week earlier (or two?) so
that the whole train could have a milestone
right before EclipseCon. Especially since the closest other milestones,
M5 Will be approximately
a full month
before EclipseCon (approx. Feb 20th?)
If it is not possible to move "in" the March 13th date, we may want to
come up with some radical plan
such as
to have an M5-prime build be "the" EclipseCon build. (M5 prime would be on the
Platform's M5,
but plus something
beyond the standard M5 delta dates, so more can be included to "show off" at
EclipseCon.
Or, maybe plain 'ol M5
is fine for the EclipseCon build, with the train's M6 to follow EclipseCon.
I raise this now, mostly just for
other projects to think about as they develop their detailed plans ... that
is,
not sure we need to solve it right
now ... but should over next few months.
Thanks,
From:
| Philippe P Mulet
<philippe_mulet@xxxxxxxxxx>
|
To:
| Cross project issues
<cross-project-issues-dev@xxxxxxxxxxx>,
eclipse.org-planning-council@xxxxxxxxxxx
|
Date:
| 07/16/2008 12:15 PM
|
Subject:
| [eclipse.org-planning-council]
[cross-project-issues-dev] Staging the next
iteration (whatever it is
named) |
Here it is again (take 3), with
fix for a missing week in M7. Allocated one more week in M7 to compensate for
EclipseCon distraction.
M1 - August 8, 2008 (6 weeks)
>>>
(3.4.1/Ganymede-SR1 +0 dates: RC1-September 1, RC2-September 8,
RC3-September 15)
M2 - September 19, 2008 (6 weeks) - PLANNING
M3 - October 31, 2008 (6 weeks) -
DEV
M4 - December
12, 2008 (6 weeks) - DEV
M5 - January 30, 2009 (7 weeks) - MAJOR FEATURE WORK COMPLETED
>>> (3.4.2/Ganymede-SR2 +0 dates: RC1-February 2,
RC2-February 9, RC3-February 16)
M6 - March 13, 2009 (6 weeks) - API FREEZE, FEATURE
TUNING, I18N & ACCESSIBILITY
>>> (EclipseCon March 23-27)
M7
- May 1st, 2009 (7 weeks) - PERFORMANCE & POLISH, BEST EFFORT ON DOC
RC1 (2 weeks) - May 15, 2009
RC2 (1 week) - May 22, 2009
RC3 (1
week) - May 29, 2009
RC4 (1 week) - June 5, 2009
__________________
Already found a typo in M1:
M1 -
August 8, 2008
M2
- September 19, 2008
M3 - October 31, 2008
M4 - December 12, 2008
M5 - January 30, 2009 (one extra
week to compensate for Christmas break)
M6 - March 13,
2009
(EclipseCon March 23-27)
M7 - April 24, 2009
RC1 - May 15,
2009
RC2
- May 22, 2009
RC3 - May 29, 2009
RC4 - June 5, 2009
Final - June 12, 2009
__________________
In parallel of the
discussion for a good name for the next iteration, I would like to know what
its staging might look like (at least for the +0 dates) ?
Here are my first
suggestions in case none was made already:
M1 -
August 10, 2008
M2 - September 19, 2008
M3 - October 31, 2008
M4 - December 12,
2008
M5 -
January 30, 2009 (one extra week to compensate for Christmas
break)
M6
- March 13, 2009
(EclipseCon March 23-27)
M7 - April 24, 2009
RC1 - May 15,
2009
RC2
- May 22, 2009
RC3 - May 29, 2009
RC4 - June 5, 2009
Final - June 12,
2009
Sauf indication contraire ci-dessus:/ Unless stated
otherwise above:
Compagnie IBM France
Siège Social : Tour Descartes, 2, avenue Gambetta,
La Défense 5, 92400 Courbevoie
RCS Nanterre 552 118 465
Forme Sociale : S.A.S.
Capital Social : 542.737.118
euros
SIREN/SIRET
: 552 118 465 02430
Sauf indication contraire ci-dessus:/ Unless stated
otherwise above:
Compagnie IBM France
Siège Social : Tour Descartes, 2, avenue Gambetta,
La Défense 5, 92400 Courbevoie
RCS Nanterre 552 118 465
Forme Sociale : S.A.S.
Capital Social : 542.737.118
euros
SIREN/SIRET
: 552 118 465 02430
_______________________________________________
cross-project-issues-dev
mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Sauf indication
contraire ci-dessus:/ Unless stated otherwise above:
Compagnie IBM
France
Siège Social : Tour Descartes, 2, avenue Gambetta, La Défense 5,
92400 Courbevoie
RCS Nanterre 552 118 465
Forme Sociale :
S.A.S.
Capital Social : 542.737.118 euros
SIREN/SIRET : 552 118 465
02430
_______________________________________________
eclipse.org-planning-council
mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
IMPORTANT: Membership in this list is generated by processes
internal to the Eclipse Foundation. To be permanently removed from this
list, you must contact emo@xxxxxxxxxxx to request removal.