Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-planning-council] Exception Process for Stardust in Kepler SR1

+1

On 28/08/2013 12:29 PM, Marc.Gille@xxxxxxxxxxx wrote:

All,

 

(Note, that the delivery of this mail got delayed significantly as I had difficulties to join this mailing list. Denis kindly assisted with these. However, we are now really under pressure to get a decision and hope for your support.)

 

we need to file for an exception process regarding Stardust in Kepler SR1:

 

The Stardust version we intend to release with Kepler SR1 will be a feature release. For a feature release we were supposed to release and have a review 1 month in advance before SR1 RC1. Otherwise an exception process has to be initiated (http://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#Planning_Council_Exception_Process) – whioch we are following now.

 

I have sent this to  SOA PMC beginning of last week and got three +1 out of four (active) members so far, the last vote possibly pending because of vacation.

I hope you can vote/decide in parallel.

 

Justification for the exception 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 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=413267) 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. Status is (might be outdated because I drew it prior to my vacation)

 

7429

awaiting_triage

P3

new

sharon....

NEW


jython Version: 2.7beta1 *Subset*

7138

awaiting_triage

P3

awai

sharon....

NEW


DataTables - Extras Version: 1.9.4

7102

awaiting_triage

P3

awai

sharon....

NEW


Datatables Version: 1.9.4

7553

new

P3

awai

emo-ip-...

NEW


Spring Framework Web MVC Version: 3.2.4.RELEASE

7423

new

P3

awai

emo-ip-...

NEW


camel-script Version: 2.9.2

 

(Jython we will be temporarily removed on our end, hence is not critical)

 

Kindly provide your +1 for this.

 

Marc

 

Dr. Marc Gille * Senior Vice President, Product Management, Infinity * Global Business Services and Technology * SunGard * 340 Madison Ave, 7th Floor, New York, NY 10173 * Phone +1 646 445 1294 * Mobile +1 347 414 4529 * marc.gille@xxxxxxxxxxx * www.sungard.com * Twitter @marcgille

 

Description: Description: Description:
                coc-signature-03-2012

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

 

 



_______________________________________________
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.


Back to the top