Rich,
I agree, it seems pointless at this stage. Let's just wait for the
processes to catch up. In any case, if a plugin/feature has a version
>= 1.0 then it's not incubating and as long as its release is/will
be reviewed, then it's graduated...
Richard Gronback wrote:
Right, my point is that if they’ll need to
undergo a review of some sort to become individual projects, which I’m
guessing they will, what’s the point of doing a graduation review on
the shell?
- Rich
On 1/22/09 6:58 AM, "Ed Merks" <ed.merks@xxxxxxxxx> wrote:
Rich,
It's not clear once components become projects if the incubation status
of the containing project remains relevant. I.e., is the Modeling top
level incubating because some subprojects are incubating? Of course
one drawback of graduating M2M itself now is that parallel IP no longer
applies to any of its components, until the execution of the processes
catches up with the documentation of the processes...
Richard Gronback wrote:
Re: [modeling-pmc] Fw: Is M2M/Operational
QVT incubating? So, which will happen first, the Foundation allowing
each “component” to become a “project” via the portal, or some
“graduation” review for an entire project that still has one of three
major components in incubation?
- Rich
On 1/22/09 4:03 AM, "Quentin Glineur" <quentin.glineur@xxxxxxx> wrote:
Hi all,
I am afraid that Declarative QVT is still in incubation.
The huge need of this project in specification make its API still
fluctuating.
Regards,
Quentin
Anthony Hunter a écrit :
Hi Team,
FYI. M2M itself
(not the components of M2M, just M2M) needs a Graduation Review
Cheers...
Anthony
--
Anthony Hunter mailto:anthonyh@xxxxxxxxxx
Software Development Manager: Eclipse Open Source Components
IBM Rational Software: Aurora / GEF / GMF / Modeling Tools
Phone: 613-270-4613
----- Forwarded by Anthony Hunter/Ottawa/IBM on
01/21/2009 10:31 PM -----
From: 
Anne Jacko <emo@xxxxxxxxxxx>
<mailto:emo@xxxxxxxxxxx>
To: 
Anthony Hunter/Ottawa/IBM@IBMCA
Date: 
01/21/2009 09:29 PM
Subject: 
Re: Is M2M/Operational QVT incubating?
Hi Anthony,
M2M Operational
QVT did graduate last year with the Ganymede release. And I just looked
in our database and see that all the components of M2M are out of
incubation. However, the process we currently use for taking projects
out of incubation is a Graduation Review. M2M itself (not the
components of M2M, just M2M) has never had a Graduation Review -- so
it's never been marked as being out of incubation.
For the M2M
project, is all the code in the components, so now that the components
have graduated, M2M should graduate as well? If this is the case, let
me know, and I'll find out if there is anything else that needs to
happen before its status can be updated. It could be that we have
simply not considered this particular situation when designing our EMO
processes (components are relatively new), and we need to update our
processes to accommodate this type of project structure. Thanks.
Anne Jacko
emo@xxxxxxxxxxx
<mailto:emo@xxxxxxxxxxx>
On Jan 21, 2009,
at 2:59 PM, Anthony Hunter wrote:
_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/modeling-pmc
_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/modeling-pmc
_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/modeling-pmc
_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/modeling-pmc
_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/modeling-pmc
|
