Merks <ed.merks@xxxxxxxxx> To:
project issues <cross-project-issues-dev@xxxxxxxxxxx>, Daniel Megert
[cross-project-issues-dev] Simultaneous release cadence change after Photon Sent
Dani, Yes, this is a statement about the train,
not about the platform. It was discussed at the Planning Council
meeting with other attendees explaining the Platform team's take on this.
But in the end, of course not all projects will even contribute specific
builds for any of the Mx or RCx builds, but there was a strong desire to
see packages built (or at the very least EPP repos built) for each Mx so
that more significant testing can occur throughout the process.
We've often been finding problems only once there are packages that allow
the milestone to be easily installed. Yes, the quality of the M1
or M3 package may be poor, but it seems better to find out about problems
sooner than than later. Regards, Ed On 16.03.2018 16:30, Daniel Megert wrote: The Eclipse top-level
project will not deliver full milestones as outlined below as this would
be way too much overhead for the team. We will only submit the bits (latest I-build) to week 3 and 9. For those
we will neither have a milestone week nor do any testing nor provide an
N&N. For week 6 we will deliver a complete milestone as we used to
in the old world. And a minor correction:"The releases
will occur end of ..." is
wrong. Correct is what's in the FAQ: "The releases will occur near
the middle of ...". Dani
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