Re: [eclipse.org-planning-council] Meeting this Wednesday

[Nick Boldt <nboldt@xxxxxxxxxx>]

I see three possible scenarios:

a) slip Oxygen.0 to July 27 (or thereabouts) to align with JDK 9 release date

b) keep Oxygen.0 June date, and add an Oxygen.0a for JDK9 fixes (gives
people only a little time to adapt to JDK 9, but doesn't impact the
'we always release in June' rule)

c) keep Oxygen.0 June date, and use Oxygen.1 for JDK 9 fixes in
September (gives people more time / summer vacation to implement
required changes)

---

Given the final release candidate for JDK 9 is due on 2017/07/06, I'd
say there's probably going to be a nearly-RC build available the same
time as the Oxygen.0 release in late June. For those who want to offer
"Early Access" support of JDK 9 in Oxygen.0, there's an opportunity to
do so in time for late June. Then that support could be hardened in
time for the September Oxygen.1 release.

For projects that don't have time / desire to do so, they could wait
until September. Or do the work in the summer and be ready for a
release on their own update site (not the Oxygen one).

---

I guess what I'm saying is...

We could offer (b) as an option to people, see who's interested via a
quick 2-question online poll, and if there's insufficient desire, fall
back to (c).

If there's sufficient desire for (b), we could then ask (second poll
question) if people are OK slipping a month instead (a), or would
prefer a second 0a release (b).



On Wed, Mar 1, 2017 at 4:35 AM, Ed Merks <ed.merks@xxxxxxxxx> wrote:
> I'm not sure the current of being able to run with Java 9, let alone
> supporting its features well in JDT:
>
>
>   https://bugs.eclipse.org/bugs/show_bug.cgi?id=493761
>
>
> I assume this must be fixed in a general way that works regardless of
> whether Java 9 is actually used or not and regardless of the JVM
> implementation provider.  Is it hopeful that this will be addressed in time
> that we may all test the state of Java 9?
>
>
> Does it really make sense to plan the whole release schedule around this
> assumption?  And as Marc suggests, is planning a release during the high
> vacation season a good plan?
>
>
>
> On 28.02.2017 18:51, Marc Khouzam wrote:
>
> +1
>
> Considering the dates are so close between Oxygen.0 and Java 9,
>
> I think having an extra release is more hassle for adopters than it is
> worth.
>
> So waiting for Java 9 is a good plan for Oxygen.0.
>
>
> One drawback I see is that more people will be on vacation at that time,
>
> but with proper planning, it should not be a problem.
>
>
> Marc
>
>
> ________________________________
> From: eclipse.org-planning-council-bounces@xxxxxxxxxxx
> <eclipse.org-planning-council-bounces@xxxxxxxxxxx> on behalf of Martin
> Lippert <mlippert@xxxxxxxxx>
> Sent: February 28, 2017 3:47
> To: Eclipse Planning Council private list
> Subject: Re: [eclipse.org-planning-council] Meeting this Wednesday
>
> +1 for moving the Oxygen.0 release to the JDK9 release date.
> Would make things for adopters of that release easier, too.
>
> Cheers,
> -Martin
>
>
>
>> Note that I've added a biggie to the list: with all the talk about having
>> an extra release to coincide with the Java 9 release, we've neglected to ask
>> why we need a release in both June and July. The Java 9 release date (which
>> by all accounts is pretty stable) is about a month after our planned Oxygen
>> date. Is there any reason why we shouldn't just move the Oxygen.0 date
>> (other than "we've always done it that way") ?
>>
>> Feel free to answer here. It would be great if you can come to the meeting
>> armed with an answer to that question.
>>
>> See you on Wednesday.
>>
>> For all phone lines: Participant conference extension: 710 then enter pin
>> 35498
>>
>> North America (toll free) 1-866-569-4992
>> Germany (local call anywhere in Germany) +49-692-2224-6059
>> France (local call anywhere in France) +33-17-070-8535
>> UK (toll free) 0800-033-7806
>> Switzerland (local call anywhere in Switzerland) +41-44-580-2115
>> SIP clients: call 710@xxxxxxxxxxxxxxxxxxxx, then enter pin 35498.
>> Wayne
>> [1] https://wiki.eclipse.org/Planning_Council/February_01_2017
>>
>> [2] https://wiki.eclipse.org/Planning_Council/March_01_2017
>>
>> --
>> Wayne Beaton
>> @waynebeaton
>> The Eclipse Foundation
>> <ConvergeLogo_Transparent.png>
>> _______________________________________________
>> eclipse.org-planning-council mailing list
>> eclipse.org-planning-council@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
> eclipse.org-planning-council Mailing List Info Page
> dev.eclipse.org
> Mailing list for private discussions amongst members of the Eclipse Planning
> Council. Using eclipse.org-planning-council To post a message to all the ...
>
>
>>
>> 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
> eclipse.org-planning-council Mailing List Info Page
> dev.eclipse.org
> Mailing list for private discussions amongst members of the Eclipse Planning
> Council. Using eclipse.org-planning-council To post a message to all the ...
>
>
>
> 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.



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