[eclipse.org-planning-council] Neon 1 - 3 / Oxygen.0.M1 - M6 draft calen

[Nick Boldt <nboldt@xxxxxxxxxx>]

First draft of Neon.1 - 3 and Oxygen.0.M1 - M6 dates are here [0] for
review, including a few conference, JDK 9, and other relevant dates.

[0] https://wiki.eclipse.org/Talk:Planning_Council/June_08_2016

I've pushed M6 a bit earlier in 2017 than this year in order to have
it arrive BEFORE Devoxx US on Mar 21-23, rather than after.

Haven't looked at Oxygen.0.M7 to Oxygen.0.Final, or the Oxygen.1/2/3
dates yet; figured there was little point until we at least agreed on
THESE dates.

If you see anything wrong or a reason to slip things forward or back a
week or so, I can adjust the wiki page. Just let me know!
Specifically, if these dates conflict with the Platform's plans [1]
for Oxygen, we obviously need to adjust something.

[1] https://www.eclipse.org/projects/project-plan.php?planurl=eclipse/development/plans/eclipse_project_plan_4_7.xml

Once David gives me access to the Google Calendar (user:
nickboldt@xxxxxxxxx, please), I can start migrating these into the
calendar so they're more easy to grok.

Cheers,

Nick

On Wed, Jun 8, 2016 at 10:05 AM, David M Williams
<david_williams@xxxxxxxxxx> wrote:
> Yes, the initial plan should to overlap exactly (that is, "release on same
> day") and see how that looks relative to the "build up" to that release day.
>
> The Update releases line up with M2, M4, and M6.
>
> And, we decided earlier no more "warm-up" RC's for update releases. RC1 only
> one week before RC2, and should be a "real" release candidate.
>
> One question I still had is if we should invent something "new" for those
> that are joining the update release for the first time -- seems to me "RC1"
> is a bit late to make their first appearance -- but, that's just a
> discussion topic.
>
> Thanks,
>
>
>
>
>
> From:        Nick Boldt <nboldt@xxxxxxxxxx>
> To:        David M Williams/Raleigh/IBM@IBMUS,
> Date:        06/08/2016 09:34 AM
> Subject:        Re: [eclipse.org-planning-council] Reminder of "nearly first
> Wednesday" meeting, June 8, 12 noon
> ________________________________
>
>
>
> David,
>
> You say Neon.1 is going to be at the same time as Oxygen M2.
>
> Does that mean that we'll have same +0,+1,+2,+3,EPP schedule for both
> Neon.1 and Oxygen.M2 (eg., both will be the week of Sep 12), and
> they'll overlap the same week?
>
> Or will they be sequential - one week we do M2, the next week we do .1
> (or vice versa) ? Eg., Oxygen.0.M2 drops the week of Sep 5, Neon.1.RC1
> the week of Sep 12, and Neon.1.Final the week of Sep 19?
>
> Do we know how many RCs (if any) are planned as warmups for Neon.1?
>
> If you can give me some ideas about what you'd like to have happen, I
> can turn those ideas into a draft schedule which we can review on the
> call today, and approve in August.
>
> Do we know which Oxygen milestones will overlap with Neon.2 and
> Neon.3? Again, I've got time today to sit down with a calendar and try
> to slot everything into the next 12 months to see where all the
> milestones and update releases will fall, if you can suggest your
> preferences & constraints.
>
> Thanks,
>
> Nick
>
>
> On Tue, Jun 7, 2016 at 5:15 PM, David M Williams
> <david_williams@xxxxxxxxxx> wrote:
>> I have an initial draft agenda at
>>
>>
> https://wiki.eclipse.org/Planning_Council/June_08_2016
>
>>
>> Nick, I have added your item to the agenda, but to answer your question,
>> Neon.1 is going to be at the same time as Oxygen M2. So, I guess we need
>> an
>> Oxygen plan first. And, doubt I will have time to create one by tomorrow,
>> much less allow time for everyone to review it. Sorry I am behind schedule
>> already!  But if you had any specific concerns, or desire, please say.
>>
>> Thanks,
>>
>>
>>
>>
>> From:        Nick Boldt <nickboldt@xxxxxxxxx>
>> To:        "eclipse.org-planning-council"
>> <eclipse.org-planning-council@xxxxxxxxxxx>,
>> Date:        06/02/2016 11:20 AM
>> Subject:        [eclipse.org-planning-council] Neon.1 schedule
>> Sent by:        eclipse.org-planning-council-bounces@xxxxxxxxxxx
>> ________________________________
>>
>>
>>
>> For next week's call on Jun 8, can we address getting dates on the
>> calendar for Neon.1 [1], and maybe even the future updates too?
>>
>> I'd like to know how many RCs will precede the Final/GA release, and
>> when in September those will be.
>>
>> [1] https://wiki.eclipse.org/Neon/Simultaneous_Release_Plan#Schedules
>>
>> Thx,
>>
>> --
>> Nick Boldt :: Productization Lead :: JBoss Tools & Dev Studio :: Red Hat,
>> Inc.
>> http://nick.divbyzero.com
>> _______________________________________________
>> 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.
>
>
>
> --
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
>
>
>
>
> _______________________________________________
> 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.



-- 
Nick Boldt :: Productization Lead :: JBoss Tools & Dev Studio :: Red Hat, Inc.
http://nick.divbyzero.com