|Re: [eclipse.org-planning-council] Simultaneous Release Brainstorming|
Hi,After a first round about reading the document, I would like that we know start by imagining whet will be the future of the SimRel.
During the call yesterday, the planning council seems to agree that an evolution of the SimRel habits would be useful and that we should give up the year long ramp up to provide a predictable short release cycle.
Some points have to be discussed then to see how we go further:* What it would be exactly ? The idea is to provide no more update but a new release each time with only one stream. In that case code names seems meaningless.
* How do we release it ? An option would be to keep only one repository in place and continuously update it which means from the users point of view new stuff with every release.
* What would be the cadence ? A quarter release (every 12 weeks) looks feasible as it is more or less corresponding to the actual milestones cadence. The main change is that those "milestones" are considered as releasable.
* How do we ensure API stability & compatibility ? When projects can make API break? How do we organize API freeze ? How do we deal with bigger features more than a release ?
* How do we organize the verification & tests in order to evolve from a by hand homologation to a more automatic one ? If we imagine that the developments could be done organized on the new release cycle, do the EDP delays, release review and manual IP log would scale ?
What do you think about how it should be organized?Please as Wayne said yesterday do not hesitate to be creative and propose new things that might be different than what we are used to do.
Best regards, https://docs.google.com/document/d/1R3RhAKMFbtBrv3KcyLV48mQJRs59GHao7XEbzZM07Jw/edit?usp=sharing
-- 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
Back to the top