| Re: [eclipse.org-planning-council] Correction re: Shipping Java 10 (18, 3) |
Where did you add it? I can't see it on https://wiki.eclipse.org/Oxygen/Simultaneous_Release_ Plan
Dani
From: Nick Boldt <nboldt@xxxxxxxxxx>
To: Eclipse Planning Council private list <eclipse.org-planning-council@eclipse.org >
Date: 09.02.2018 17:51
Subject: Re: [eclipse.org-planning-council] Correction re: Shipping Java 10 (18, 3)
Sent by: eclipse.org-planning-council-bounces@xxxxxxxxxxx
I've added Oxygen.3a RC1 +0 on Mar 23, and GA on Apr 11. If I get bored I'll start filling in the other dates in between... does anyone know of a way to import a series of events to Google Calendar so they don't have to be done manually one-by-one?
Nick
On Fri, Feb 9, 2018 at 9:10 AM, Daniel Megert <daniel_megert@xxxxxxxxxx> wrote:
Dear Planning Council
Please note that there was a mistake in the proposed schedule for Update 3a. The GA date will be April 11 and not April 4. The quiet days were missing.
Dani
----- Forwarded by Daniel Megert/Zurich/IBM on 09.02.2018 15:08 -----
From: Daniel Megert/Zurich/IBM
To: "Eclipse Planning Council private list" <eclipse.org-planning-council@eclipse.org >
Date: 29.01.2018 17:23
Subject: Shipping Java 10 (18,3)
Dear Planning Council
As I already mentioned in previous Planning Council meetings, Java 10 (18.3) will ship at almost the same date as Oxygen Update 3 (4.7.3) on March 20. We discussed in the Eclipse top-level PMC how we want to deliver the Eclipse support for Java 10 (18.3). The consensus was that we need an Update 3a, like we had Update 1a. This allows other projects, like WTP, to also contribute their changes for Java 10 (18.3).
Only projects providing changes needed for Java 10 (18.3) can participate in this release.
I propose the following schedule, which follows the schedule for Update 1a:
+0 on Friday
+1 on Monday
+2 on Tuesday
+3 on Wednesday
EPP on Thursday
Complete RC Available on (next) Friday
RC1 +0: Friday, March 23
RC2 +0: Friday, March 30
GA: Wednesday, April 4
Please approve this plan or disapprove with well-founded arguments.
Dani
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@eclipse.org
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@xxxxxxxxxxxto request removal.
--Nick Boldt
Senior Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
IM: @nickboldt / @nboldt / http://nick.divbyzero.com
TRIED. TESTED. TRUSTED.
@ @redhatnews Red Hat
“The Only Thing That Is Constant Is Change” - Heraclitus
_______________________________________________ https://urldefense.proofpoint.
eclipse.org-planning-council mailing list
eclipse.org-planning-council@eclipse.org com/v2/url?u=https-3A__dev. eclipse.org_mailman_listinfo_ eclipse.org-2Dplanning- 2Dcouncil&d=DwICAg&c=jf_ iaSHvJObTbx-siA1ZOg&r= 1UITCR5rxUZHSFczvfaNFK4ymEbEic cRX7VKchpqz0Y&m=n45kPgh55- TgTMTk9ZPQkFhdKyvQSP- wzQYXIDdEGno&s=ZrAkRC-g7aYKG_ LuqIPvxbb3-Qmv8SpVhTt80-QrCHI& e=
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@eclipse.org
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
Senior Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
IM: @nickboldt / @nboldt / http://nick.divbyzero.com