Re: [eclipse.org-planning-council] Reminder of First Wednesday Meeting,

[Doug Schaefer <dschaefer@xxxxxxx>]

From: Daniel Megert <daniel_megert@xxxxxxxxxx>

Reply-To: Eclipse Planning Council <eclipse.org-planning-council@xxxxxxxxxxx>
Date: Wednesday, May 6, 2015 at 10:38 AM
To: "mike.milinkovich@xxxxxxxxxxx" <mike.milinkovich@xxxxxxxxxxx>, Eclipse Planning Council <eclipse.org-planning-council@xxxxxxxxxxx>
Subject: Re: [eclipse.org-planning-council] Reminder of First Wednesday Meeting, May 6, 12 Noon.

> Waiting nine months to June  2017 would not be good for anyone.

I completely agree. Note that when Java 7 GAed in September, we approved to ship the support with SR1 in September.

I remember that being less than ideal. Add support for a new Java major release is a pretty big deal that shouldn’t be hidden in a service release.

Dani



From:        Mike Milinkovich <mike.milinkovich@xxxxxxxxxxx>
To:        eclipse.org-planning-council@xxxxxxxxxxx
Date:        06.05.2015 16:32
Subject:        Re: [eclipse.org-planning-council] Reminder of First Wednesday Meeting, May 6, 12 Noon.
Sent by:        eclipse.org-planning-council-bounces@xxxxxxxxxxx

---

I think that this thread is very timely. The fact that Java 9 has now
slipped into Sept. 2016 means that a full Eclipse release which supports
it soon afterwards would be very important. Waiting nine months to June
2017 would not be good for anyone.

I am not sure if anyone has actually thought about when we might
implement such a change, but May/November 2016 releases would make a lot
of sense to me given what we know about the Java 9 plans.


--
Mike Milinkovich
mike.milinkovich@xxxxxxxxxxx
+1.613.220.3223 (mobile)

_______________________________________________
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.