All,
we need to file for an exception process regarding Stardust in Kepler SR1:
I am sending this to the SOA PMC and will submit to the Planning Council after to get approval regarding the above.
Justification is:
· Most of the added functionality was already in the Stardust 1.0 code base we released with Kepler (e.g. the BPMN2 metamodel support). It was just not exposed as APIs or in the UI.
· Other functionality (e.g. the Apache Camel integration) was part of the original SunGard codebase, but was not checked in because of pending CQs for required third-party libraries.
· No other Eclipse project and especially no functionality in other projects releasing with SR1 will be affected.
· The community and other projects will benefit from the enhancements (e.g. Mangrove and BPMN2 Editor from the BPMN2 enhancements or the proposed Winery project from general enhancements in the Browser Modeler).
We would be aiming at the following schedule:
· RC1 + 3 (21.08.) Contribute all new features
· RC2 + 3 (04.09.) Contribute some cleanup work in portal area + late fixes
We are confident after communication with Eclipse Legal that all of our pending CQs for third party libraries will be resolved by then.
Kindly provide your +1 for this.
Marc
Join the online conversation with SunGard’s customers, partners and industry experts and find an event near you at: www.sungard.com/ten.
CONFIDENTIALITY: This e-mail (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you receive this e-mail in error, please notify the sender and delete this e-mail from your system.
SunGard Systeme GmbH • Registered: Frankfurt am Main, Handelsregister Frankfurt HRB 56839 • Geschäftsführer: Harold Finders, Christian U. Haas, Henry Morton Miller Jr., Victoria E. Silbey
