Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-scripting-dev] Requesting a stable update site for EASE

On Wed, Nov 20, 2013 at 3:30 PM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:
They look exactly like official releases to me. They're labeled "Release Builds" on the project download page.

That's because the page was copied from the eclipse project.  That's the easiest thing to fix.


According to the EDP (section 6.4):

"Official Releases are the only downloads allowed to be labeled with x.y, e.g., 0.5, 1.0, 2.3, etc."

As is this. (0.14-checkpoint for example).
"Under no circumstances are builds and milestones to be used as a substitute for doing proper official Releases. Proper Release management and reviews is a key aspect of Eclipse Quality."

This is harder.  I wouldn't want to break the spirit of this requirement, but need checkpoints to widen the adoption of E4 incubator projects both to promote stability and to separate out the different phases of the incubator projects (some checkpoints work with Juno, some with Kepler, and soon to be some with Luna).  I'm open to suggestions.

But their not release quality, we release these different components by graduating them into the Eclipse project proper (or as you say the graduate to their own project, like Orion).

But then it's semantic quibbling.  What's the difference between a release and a checkpoint except with our checkpoint we don't guarantee quality or provide proper bookkeeping, we just provide stable consumable update sites.


Paul Webster
Hi floor.  Make me a sammich! - GIR

Back to the top