Re: [eclipse.org-planning-council] Simultaneous Release Brainstorming

[Nick Boldt <nboldt@xxxxxxxxxx>]

FAQ looks good. I've added a few changes in suggest mode to fluff up a few answers and tweak the English a bit for clarity. Also one comment the day of the month we're targeting for GA releases.

Email template also looks good. You could add a note about Week 12 if you want to specifically mention Quiet Week (AKA Blocker Respin Week).

For the BZ to be created, I provided some verbeage in the FAQ you could copy and paste into the BZ, or even move there entirely if you prefer it live in the BZ than the FAQ.

Cheers,

Nick

On Thu, Mar 8, 2018 at 8:53 AM, Mélanie Bats <melanie.bats@xxxxxxx> wrote:

Hi,

I updated the FAQ according to what we discussed yesterday in the call, please review it : https://docs.google.com/document/d/1IVA59E5bxv1l1W1ZTSZMUUH7IKIO-mRLEGn1bVO-dFs/edit?usp=sharing

Main changes :
* Milestones: in the cycle instead of checkpoints
* Naming : I will open a bugzilla to track the discussion about that point
* Tracking and opt-in process

I will put the FAQ on the wiki tomorrow.

I will send also tomorrow the following mail to cross-project :
"Hi,

The planning council has decided to change the simultaneous release cadence after Photon to give up with the year long ramp-up to the release for a rolling release.

After Photon, we will move from a 1 year release cycle to a 13 weeks cycle. The releases will occur end of June, September, December and March each year.

There are many different motivations to update the release cadence. The main ones are:
* Ease the update from one release to another for the end user
* Let developers provide new features faster to their users
* Simplify the maintenance by keeping only one stream for contributors

The release cycle would be :
M1 Friday    Week 3
M2 Friday    Week 6
M3 Friday    Week 9
RC1 Friday   Week 10 : API & Feature freeze
RC2 Friday   Week 11 : Only fixes, all code is done by the end of RC2
GA Wednesday Week 13

Due to this rolling release, our yearly code name pattern does not make sense anymore. This is still under discussion a bugzilla is open to continue the discussion on this topic: xxxxx

A FAQ is available on the wiki to answer the most common questions about this new cycle :
https://wiki.eclipse.org/SimRel/Simultaneous_Release_Cycle_FAQ

Best regards"

Thanks for your reviews,
--
Mélanie Bats
CTO
+33 7 87 69 42 84

+33 5 34 57 16 29
@melaniebats

*Obeo*
25 Boulevard Victor Hugo - Colomiers - France
http://www.obeo.fr
_______________________________________________
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

TRIED. TESTED. TRUSTED.

@ @redhatnews      Red Hat

“The Only Thing That Is Constant Is Change” - Heraclitus