Works for me

Jeff 

Le 5 févr. 2018 15:35, "Nick Boldt" <nboldt@redhat.com> a écrit :

Any objections to the dates proposed to the Planning Council below?

April 4 (Oxygen.3a GA day) lands in the middle of Sprint 147 (Heather Train, final sprint to GA). 

I'll be on PTO Mar 30-Apr 8, but we can update to:

* Oxygen.3a.RC1 on Mar 29, then 

* Oxygen.3a.GA on Apr 9. 

This will give us:

* over a week to test the RC while I'm AFK, then 

* 2 days to review the final target platform update.

GA sprint date reminders:

* Apr 11 :: GA code freeze for Devstudio 11.3.0.GA / JBT 4.5.3.Final

* Apr 17 :: GA complete

* Apr 24 :: GA announcement

Google Calendar: 

* http://bit.ly/rhdtrain or http://bit.ly/rhdtrain0

JIRA schedules: 

* http://bit.ly/devstudiocalendar or http://bit.ly/jbosstoolscalendar

Nick

---------- Forwarded message ----------
From: Daniel Megert <daniel_megert@ch.ibm.com>
Date: Mon, Jan 29, 2018 at 11:24 AM
Subject: [eclipse.org-planning-council] Shipping Java 10 (18,3)
To: Eclipse Planning Council private list <eclipse.org-planning-council@eclipse.org>


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@eclipse.org to 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

_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev