Yes, the goal all along was to graduate this tooling into a mature project (PDE?) when it is ready. The e4 incubator doesn't do formal releases, but it is useful to mark the version of the incubator content that aligns with a given platform release.. We have been using the "0.12" tag/repository in e4 to indicate that.
John Wayne Beaton <[email protected]> Sent by: [email protected] 06/28/2012 10:25 AM Please respond to E4 Project developer mailing list <[email protected]> To [email protected] cc Subject Re: [e4-dev] master is open for UI, Runtime, and Tools If technology in the e4 incubator is maturing to the point where there are releases, you should consider moving it out of the incubator. The EDP states that incubator projects "never have releases". If this is a rule that we need to revisit, I'm game to have that discussion. Wayne [1] http://www.eclipse.org/projects/dev_process/development_process_2011.php#4_9_Incubators On 06/28/2012 06:27 AM, Paul Webster wrote: On Thu, Jun 28, 2012 at 4:17 AM, Lars Vogel <[email protected]> wrote: Hi Paul, If we commit something to the Eclipse e4 tooling will it be automatically in Eclipse 4.2.1? That would be e4 0.12.1 But we don't have a plan for 0.12.1 yet. 1) what do we want to include 2) what kind of delivery date Later, PW -- Paul Webster Hi floor. Make me a sammich! - GIR _______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton Explore Eclipse Projects_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
