> I am not
sure I understand the comment that the release would need to be "much
Compared to what people/companies were
used to with our SR2 dates.
Just to be clear, I'm also in favor
of having Java 9 in Neon.3 :-)
Mike Milinkovich <mike.milinkovich@xxxxxxxxxxx> To:
05.07.2016 15:34 Subject:
Planning the release dates for Oxygen.0 and Neon.X update releases Sent by:
I would like to suggest that it would be very good for the Eclipse IDE
to time its Neon.3 release to include Java 9 support.
Java 9 release March 23, 2017. The proposed date below for Neon.3 is March
17, 2017. I am not sure I understand the comment that the release would
need to be "much later"?
On 2016-07-05 03:19 AM, Daniel Megert wrote: Ideally we would like to ship Neon.3
with Java 9 support, but I see that this would make it available much later
than our usual SR2s.
* - This means we have Neon.1 released the week before we release Oxygen.0.M2, which provides some buffer/breathing space.
** - But for Neon.2 and Oxygen.0.M4, they're slated to land on the same date - Dec 16. We could push one a week later but that's dangerous with holidays affecting developer availability. Therefore, we might need to move one of those a week earlier. If so, which one -- Oxygen.0.M4 or Neon.2?
*** - The other possible conflict is around Oxygen.0.M6, which drops around the same week as Devoxx US (2017/03/21 to 03/23), JDK 9 GA (2017/03/23), and the week after Neon.3. Should we move that one too, or is having Neon.3 just before Devoxx and M6 right after it a reasonable approach? (We could switch them and even add another week for Neon.3, since it's the LAST update for Neon and needs to definitely work with JDK 9. Therefore: Oxygen.0.M6: 03/17 or 03/24; Neon.3: 03/30.)
Another thing we could do is move the GA dates for the update releases to Wednesdays instead of Fridays, so there can be a better marketing splash mid-week.