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

[David M Williams <david_williams@xxxxxxxxxx>]

> Anyway, you guys have done it this way for ages and it basically works
> for you so its fine...just odd and amazing to witness.

It is amazing it works. In the "cool, that's amazing" sense.

But, I want to remind you, Jesse, you should say "us guys" now. :)  You are in a prime position to help improve things.

As we finish Juno and begin Kepler, it is a good time for all Planning Council members to be thinking of some concrete suggestions to improve things, so I will look forward to those discussions ... in August and September (not now) ... between now and third quarter is a good time to have in-depth talks with the projects and strategic members you represent to see what they would like improved and then "abstract" those into a planning council requirements, topics, or proposals.

Greatest regards,




Jesse McConnell ---05/24/2012 04:06:01 PM---> First, that locking down a large set of software and releasing together is > anachronistic, and se

From: Jesse McConnell <jesse.mcconnell@xxxxxxxxx>
To: "eclipse.org-planning-council" <eclipse.org-planning-council@xxxxxxxxxxx>,
Date: 05/24/2012 04:06 PM
Subject: Re: [eclipse.org-planning-council] Does Simultaneous release mean that we release on the same day
Sent by: eclipse.org-planning-council-bounces@xxxxxxxxxxx

---

First, that locking down a large set of software and releasing together is anachronistic, and second that "being loosey-goosey" with what gets resolved is scary. 

no, that trying to develop everything all at once and have everything under the sun release at once on the same magical day is anachronistic

this goes hand in hand with the 'loosey-goosey' comment because you have versions of software up and down the entire stack in flux until the very end...and osgi+p2 encourage it by the idea that your software is dependent on some open range of versions and its not until you build that you end up with a specific version, couple that with non-durable repositories of artifacts that come and go....

call me old fashioned but I rather like depending on version 4.8.1 of junit and updating to 4.8.2 should be a conscious decision of mine...maybe I am the anachronism in that respect :) 
 
cheers,
jesse
_______________________________________________
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.