From: eclipse.org-planning-council-bounces@xxxxxxxxxxx [mailto:eclipse.org-planning-council-bounces@xxxxxxxxxxx] On Behalf Of John Arthorne
Sent: June-28-11 11:28 AM
To: eclipse.org-planning-council
Subject: Re: [eclipse.org-planning-council] Reminder no July meeting ... but, Juno M1 is coming! (in August)
The other thought I had is to "donate" the extra week to M3, to account for the expanded EclipseCon Europe. Of course that also results in an M4 two days before Christmas. In any case, as long as I know M1 and M2 I can survive until our next planning call in August ;)
John
David M Williams <david_williams@xxxxxxxxxx>
Sent by: eclipse.org-planning-council-bounces@xxxxxxxxxxx 06/27/2011 11:18 AM Please respond to
"eclipse.org-planning-council" <eclipse.org-planning-council@xxxxxxxxxxx> |
| To | "eclipse.org-planning-council" <eclipse.org-planning-council@xxxxxxxxxxx> | cc | | Subject | Re: [eclipse.org-planning-council] Reminder no July meeting ... but, Juno M1 is coming! (in August) |
|
Yes, M4 has always been "tricky" with the year-end holidays, and the fact we move from two week window to one. So there's a double squeeze. (I think the +0 dates would still be 6 weeks, at M4). So, I'm fine with discussing, but would not want to move 12/16 to 12/23 just to make it "look good on paper" since I think a lot of teams are at least partially on holiday that week ending with 12/23. And none of the >+0 teams have requested longer times in the past ... but, I am open to suggestions and don't mean to cut off discussions about it. As long as its useful and meaningful to the teams you represent ... I'm sure we can get someone to promote the build on 12/23. :)
As for the 8 week M7 cycle ... yes, I knew that'd jump right out at you :) [And, it is, in fact, the reason I added the "elapsed weeks" column!] And, I wasn't sure what to do, exactly. As you can imagine, I always simply follow the previous years dates, always needing to adjust a day or two to keep cycles aligned with days of the week. But, when it came to Juno's end dates ... is seems that with the way the "4th Wednesday" occurs in 2011 and 2012, we essentially gain, nearly, a full week. From June 22 to June 27. So ... I worked backward from there, putting the "extra week" in M7, but, granted, would be a good one to discuss. and I'm fine putting the extra time somewhere else, that's meaningful.
As you said, my main purpose, for now, was just to get the first few milestones lined up, since we will need to by in sync to make those "simultaneous".
Thanks for your quick review.
From: John Arthorne <John_Arthorne@xxxxxxxxxx>
To: "eclipse.org-planning-council" <eclipse.org-planning-council@xxxxxxxxxxx>
Date: 06/27/2011 10:23 AM
Subject: Re: [eclipse.org-planning-council] Reminder no July meeting ... but, Juno M1 is coming! (in August)
Sent by: eclipse.org-planning-council-bounces@xxxxxxxxxxx
In your proposed milestone dates, you have a 5-week M4 cycle, and an 8-week M7 cycle. Adding an extra week for EclipseCon makes sense, but two extra weeks seems like overkill. I suggest moving M4-M6 one week later, which makes M4 a regular 6-weeks, and gives 7 weeks for M7. Of course as you say we can tweak this once the EclipseCon dates are known. My immediate concern is figuring out M1-M3 so we can start planning our Juno work. I am fine with the M1-M3 dates you propose.
John
David M Williams <david_williams@xxxxxxxxxx>
Sent by: eclipse.org-planning-council-bounces@xxxxxxxxxxx 06/26/2011 10:37 PM Please respond to
"eclipse.org-planning-council" <eclipse.org-planning-council@xxxxxxxxxxx> |
| To | "eclipse.org-planning-council" <eclipse.org-planning-council@xxxxxxxxxxx> | cc | | Subject | [eclipse.org-planning-council] Reminder no July meeting ... but, Juno M1 is coming! (in August) |
|
Just a reminder that we will not be meeting in July. Our next meeting will be August 3, 2011 (our regular "first Wednesday" meeting, at Noon Eastern).
But also wanted to present our tentative Juno milestone dates. This is both so you can review before our August meeting, but more so to serve as a reminder that we will be producing a "simultaneous M1" and it will be due shortly after our August meeting. Please work with the projects you represent to remind them that "Simultaneous Release" means more than just achieving the final release date ... we strive for continuous participation in each milestone.
We'll discuss and finalize the Juno dates in August. In the meantime, I hope everyone enjoys a well deserved break in July. Congratulations and thanks again for the Indigo release.
= = = = =
End Date Span Elapsed Weeks
M1 Friday, August 19, 2011 08/05 to 08/19 8 (from previous release GA)
M2 Friday, September 30 09/16 to 09/30 6 (from M1)
M3 Friday, November 11 10/28 to 11/11 6 (from M2)
M4 Friday, December 16 12/09 to 12/16 5 (from M3) (shift from 2 week window to 1 week window)
M5 Friday, February 03, 2012 01/27 to 02/03 7 (from M4)
M6 Friday, March 16 03/09 to 03/16 6 (from M5)
EclipseCon! ?? ??/?? to ??/?? * dates may be shifted, once EclispeCon dates are known
M7 Friday, May 11 05/04 to 05/11 8 (from M6)
RC1 Friday, May 25 05/18 to 05/25 2 (from M7)
RC2 Friday, June 01 05/25 to 06/01 1 (from RC1)
RC3 Friday, June 08 06/01 to 06/08 1 (from RC2)
RC4 Friday, June 15 06/08 to 06/15 1 (from RC3)
Quiet time, June 16 to June 27
(no builds during "quiet time", assumed all code is done by end of RC4
Release Wednesday, June 27, 2011
_______________________________________________
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. _______________________________________________
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. _______________________________________________
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.
