Re: [eclipse.org-planning-council] Does Simultaneous release mean that w

[David M Williams <david_williams@xxxxxxxxxx>]

It is a bit weird. I'm not sure of their reasoning, and not sure there could ever be absolute rules about it or how to enforce it; that is, I think it might be "ok" sometimes.

But, there's several parts of the "simultaneous" part that could easily be "messed up". For one, did they have third party bundles? Did they use the "released" ones from Orbit? Or ones from an I build? Seems unlikely they used released versions, since Orbit has not produced final "R build" for Juno yet, .... though ... it is possible the ones they use haven't have not changed in a long time and would still be valid?

My greatest concern would involve testing. One of the main benefits of the simultaneous release is that "the stack" gets all tested together. And this works both directions. Perhaps they have a bug that won't show up until some of final builds from the Platform, or vice versa, perhaps the Platform introduces a regression that would not be discovered in time, if they are doing their main testing in April and then there would be no chance to fix it until Juno SR1.

But, I do think there can be valid reasons for it. Perhaps some projects have simple dependencies that are unlikely to "break" and, most important, perhaps their adopters/committers really need a release in May for some business reason. In those cases, I'd still expect the project to continue testing through the final Simultaneous Release, which implies more work for them over all .... but ... if they have a business need .... that's hard to argue with. And perhaps they are fully prepared to come out with a a quick maintenance release by June if needed?

Not to mention ... part of the purpose of the Simultaneous Release is to stream line work for Eclipse Foundation and others, so if you started having dozens of releases a month or two early, you'd lose some of that stream line effect.

I think the right action in such cases is for the project's mentors and PMC to have a deep discussion with the project and make sure they understand the implications and responsibilities.

Hope some of these points are helpful.



Wayne Beaton ---05/23/2012 09:48:33 PM---In my mind, "simultaneous release" means that projects all release at the same time (i.e. the same d

From: Wayne Beaton <emo@xxxxxxxxxxx>
To: "eclipse.org-planning-council" <eclipse.org-planning-council@xxxxxxxxxxx>,
Date: 05/23/2012 09:48 PM
Subject: [eclipse.org-planning-council] Does Simultaneous release mean that we release on the same day
Sent by: eclipse.org-planning-council-bounces@xxxxxxxxxxx

---

In my mind, "simultaneous release" means that projects all release at the same time (i.e. the same day).

Several projects opt to do releases in advance of the actual simultaneous release and basically just coast into the simultaneous release date. I find this a little weird.

soa.bpel comes to mind as a for-instance. They did their 1.0 release/graduation on May 2/2012.

Does anybody else think that this is weird? Do I just need to get over it?

Wayne
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
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.