Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] Next Eclipse Planning Councilmeeting: September 6

* Java 9 release (by Dani Megert)

Here's a possible schedule for Oxygen Update 1a (Java 9 and JUnit 5):

Eclipse Oxygen .1a (Java 9 and JUnit 5)
        - GA Wednesday, October 11
        - RC1 on Friday, September 29, Platform RC1 on Friday, September 22
        - RC2 on Friday October 6, Platform RC2 on Friday, September 29 (expected final build)

NOTE 1: We can't do earlier RCs because Java 9 goes GA on September 21, and before that, we can't merge the code.
NOTE 2: Schedule is very tight - maybe move GA to October 18?
NOTE 3: If the infrastructure is as bad as it is these days, those dates will be missed.

I suggest to discuss and finalize this in the call next week. I won't be available until September 11.

It would also be good if the projects that plan to contribute Java 9 and/or JUnit 5 changes to Oxygen 1a come forward and announce this.


From:        Mélanie Bats <melanie.bats@xxxxxxx>
To:        Eclipse Planning Council private list <>
Date:        30.08.2017 12:22
Subject:        [] Next Eclipse Planning Council        meeting: September 6
Sent by:


Next Eclipse Planning Council meeting will be on Wednesday, September

The main topics on the agenda are :
* Oxygen.1 status (by Fred Gurr/Mikael Barbero)
* Photon update (by Fred Gurr/Mikael Barbero)
* Java 9 release (by Dani Megert)
* Brainstorm about the future of the SimRel (by Mélanie Bats)

Please if you have other items let me know.

The minutes from the August meeting are available on the wiki:

The call informations and the agenda are available on the meeting page:

See you next week.
Mélanie Bats
Eclipse Modeling Consultant
+33 5 34  57 16 29

25 Boulevard Victor Hugo - Colomiers - France
_______________________________________________ mailing list

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.

Back to the top