Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [modeling-pmc] MDT (EODM, UML2 Tools) Graduation


+1

Kenn Hussey

Senior Software Developer
Rational Software, IBM Software Group

770 Palladium Drive
Kanata, Ontario, K2V 1C8

T: (613) 599-3980  F: (613) 599-3912



Richard Gronback <richard.gronback@xxxxxxxxxxx>
Sent by: modeling-pmc-bounces@xxxxxxxxxxx

06/07/2007 09:54 AM

Please respond to
PMC members mailing list <modeling-pmc@xxxxxxxxxxx>

To
PMC members mailing list <modeling-pmc@xxxxxxxxxxx>
cc
Subject
Re: [modeling-pmc] MDT (EODM, UML2 Tools) Graduation





Thanks, Kenn.  I agree with you that #2 is the right option at this time.

Best,
Rich


On 6/7/07 9:51 AM, "Kenneth Hussey" <khussey@xxxxxxxxxx> wrote:


Rich,

At this point, I think the options are as follows:

1. Approve graduation of the component(s) and proceed to have the Foundation conduct the review. In this case the version numbers of these components would remain as is (2.0 for EODM and 1.0 for UML2 Tools).

2. Deny graduation of the component(s) but release them as part of Europa. In this case, the version numbers will need to be changed (e.g. 0.9 for EODM, 0.8 for UML2 Tools).

3. Deny graduation of the component(s) and not release them as part of Europa. In this case, the version numbers could stay the same, but the components would no longer be following the schedule of the MDT project (and Europa release).

I personally thing that option 2 is the right choice for both components. Back when we were planning the 1.0 release of MDT, we optimistically chose to target 2.0 and 1.0 for EODM and UML2 Tools in anticipation that they would be ready to exit incubation come release time. We were fully prepared to deal with the possibility that they would not be ready to graduate. Either way, we need to make a decision so that if we need to change version numbers (for example), we can do so sooner than later (e.g. before I sent out my legal certification for these components).

Kenn Hussey

Senior Software Developer
Rational Software, IBM Software Group

770 Palladium Drive
Kanata, Ontario, K2V 1C8

T: (613) 599-3980  F: (613) 599-3912



Richard Gronback <richard.gronback@xxxxxxxxxxx>

Sent by: modeling-pmc-bounces@xxxxxxxxxxx
06/07/2007 09:43 AM

Please respond to
PMC members mailing list <modeling-pmc@xxxxxxxxxxx>

To

PMC members mailing list <modeling-pmc@xxxxxxxxxxx>

cc
Subject

Re: [modeling-pmc] MDT (EODM, UML2 Tools) Graduation




Yes, but there could not a “previous release” or else they wouldn’t just now be exiting incubation, right?  It seems this is the first actual release, and I see previous 0.8 downloads, so to me it makes sense for this to be 1.0.

Regarding UML2 Tools, I don’t think it’s ready to exit incubation, actually.  Taking a look at the 3 communities, it’s still looks like an incubator.  For development, we have 1 committer from 1 company, along with 2 active contributors from the same company (not so diverse).  For adopters, I don’t know of any commercial products yet building on UML2 Tools.  From the newsgroup activity, the user community still seems fledgling.  Then, there’s the fact that although Michael, Tanya, and Sergey have made great progress with the 4+ diagrams, it’s still a subset of UML2 diagrams.  In conclusion, I guess I don’t see how spending another release cycle in incubation for this component is a bad thing.

And then there’s the Europa train... As UML2 Tools is on the train, it is supposed to be released (exiting incubation) in order to be a part.  This presents a complication, but at the same time seems no different than last year when GMF itself released/exited incubation but shipped EMFT components that were not yet out of incubation.  This year, it would seem that MDT is in this boat, releasing in Europa some new components are incubating.  The version number for UML2 Tools would need to reflect this (even a number approaching but not yet an official 1.0.0).  Other thoughts?

I’m not too familiar with the status of EODM, so will defer to others to comment until I can take a closer look.

Best,
Rich


On 6/7/07 9:11 AM, "Kenneth Hussey" <khussey@xxxxxxxxxx> wrote:



Rich,

I believe the only restriction is that a major version number (i.e. anything before the first dot) cannot be used if still in incubation. We chose "2.0" for EODM because the API, and specification version that it conforms to, is quite different from the previous release.

Cheers,

Kenn Hussey

Senior Software Developer
Rational Software, IBM Software Group

770 Palladium Drive
Kanata, Ontario, K2V 1C8

T: (613) 599-3980  F: (613) 599-3912



Richard Gronback <richard.gronback@xxxxxxxxxxx>

Sent by: modeling-pmc-bounces@xxxxxxxxxxx 06/07/2007 08:51 AM
Please respond to
PMC members mailing list <modeling-pmc@xxxxxxxxxxx>
To
PMC members mailing list <modeling-pmc@xxxxxxxxxxx>
cc
Subject
Re: [modeling-pmc] MDT (EODM, UML2 Tools) Graduation




Hi Kenn,

I guess I missed part of this conversation and outcome along the way, but how can EODM be using the 2.0 release number if it’s not yet out of incubation?  Shouldn’t they both be graduating and releasing a 1.0 version?

Thanks,
Rich


On 6/7/07 8:44 AM, "Kenneth Hussey" <khussey@xxxxxxxxxx> wrote:


I hereby request approval for the EODM and UML2 Tools components of MDT to graduate from incubation to that we be declare 2.0 and 1.0 releases, respectively, as part of the upcoming 1.0 release of MDT.

Thanks,

Kenn Hussey

Senior Software Developer
Rational Software, IBM Software Group

770 Palladium Drive
Kanata, Ontario, K2V 1C8

T: (613) 599-3980  F: (613) 599-3912


_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/modeling-pmc




--
Richard C. Gronback
Borland Software Corporation
richard.gronback@xxxxxxxxxxx
+1 860 227 9215
_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/modeling-pmc


Back to the top