[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [modeling-pmc] Project plan
|
Hi Kenn,
I think the roll-up you have is better than linking, honestly. I think it
would be possible to merge several component plans automatically, though I
stuck with the simple approach first. Of course, your project would have to
agree upon a certain structure and query style, which you've done.
But again, I'm waiting to see what happens to the portal to support
components -> projects in the future beyond going any further. Of course,
I'm sure additional patches are always welcome ;)
Best,
Rich
On 11/10/08 9:24 AM, "Kenn Hussey" <Kenn.Hussey@xxxxxxxxxxxxxxx> wrote:
> Rich,
>
> Thanks, this will help us drill down into the "sub" plans. But I still see
> value in seeing all the plan items at the parent project level, from a "bird's
> eye" view. I was thinking it would be useful to include the component name for
> each bug that appears in a plan; this way, in the rolled up plan (like the one
> for MDT), it would be possible to tell which component each bug is from. What
> do you think?
>
> Cheers,
>
> Kenn Hussey
> Program Manager, Modeling and Design Solutions
>
> Embarcadero Technologies, Inc. | www.embarcadero.com
> 82 Peter Street, Second Floor | Toronto, ON M5V 2G5
> Kenn.Hussey@xxxxxxxxxxxxxxx
> Office: 416-593-1585 x9296 Mobile: 613-301-9105
>
>
> -----Original Message-----
> From: modeling-pmc-bounces@xxxxxxxxxxx
> [mailto:modeling-pmc-bounces@xxxxxxxxxxx] On Behalf Of Richard Gronback
> Sent: Sunday, November 09, 2008 11:15 AM
> To: PMC members mailing list
> Cc: Bjorn Freeman-Benson
> Subject: Re: [modeling-pmc] Project plan
>
> Hi,
>
> I've created a patch that will let us use a full plan url and specify a
> component name: https://bugs.eclipse.org/bugs/show_bug.cgi?id=254692
>
> Hopefully, Bjorn will be able to commit this shortly and thereby enable our
> master-detail plan structure until such time components can be declared as
> projects through the portal.
>
> Note that components will need to use their project id in the plan.xml and
> not some component namespace (e.g. modeling.emf and not modeling.emf.teneo).
>
> And just to clarify one more thing regarding the upcoming Galileo release...
> The Planning Council is the body that coordinates the simultaneous releases,
> and is comprised of members from each PMC. Therefore, please ask Ed and/or
> myself for what you need to facilitate your project/component's
> participation. As each project lead is on our PMC, everyone should have
> representation.
>
> Thanks,
> Rich
>
>
> On 11/8/08 3:06 PM, "Cédric Brun" <cedric.brun@xxxxxxx> wrote:
>
>> Hi Rich,
>>
>> Just speaking about EMFT but that's probably the same issue for the
>> other projects, but the plan urls given in the portal are :
>>
>> http://www.eclipse.org/modeling/emft/compare/project-info/plan.xml
>> http://www.eclipse.org/modeling/emft/ecoretools/project-info/plan.xml
>> http://www.eclipse.org/modeling/emft/jcrm/project-info/plan.xml
>> http://www.eclipse.org/modeling/emft/mwe/project-info/plan.xml
>> http://www.eclipse.org/modeling/emft/texo/project-info/plan.xml
>>
>> Though only the ecore tools appears on the link you provided.
>> Probably an issue or a misunderstanding about how those plans should be
>> merged don't you think ?
>>
>> Cédric
>>
>> Richard Gronback a écrit :
>>> Hi,
>>>
>>> I created an initial roll-up Modeling project plan:
>>> http://www.eclipse.org/projects/project-plan.php?projectid=modeling
>>>
>>> Perhaps we can just contribute this one plan link to the Galileo plan and
>>> indicate on our plan which are train participants?
>>>
>>> Some things I noticed from the list of individual project links:
>>>
>>> - modeling.emf only talks about Teneo
>>> - modeling.m2m only talks about ATL (no QVTO)
>>> - modeling.m2t only talks about MTL (no Xpand or JET)
>>> - modeling.tmf only talks about Xtext (no TCS)
>>> - modeling.emft only talks about Ecore Tools
>>> - modeling.gmt does not exist!
>>>
>>> Please note that all projects are required to have a plan.xml to pass their
>>> annual release/continuation review, not only release train projects.
>>> Furthermore, if you're waiting on the portal to allow components to switch
>>> to projects, it will be some 6+ months. So, we'll need to manually roll-up
>>> project components into a single plan (see the MDT plan for a nice example).
>>>
>>> Thanks,
>>> Rich
>>>
>>> _______________________________________________
>>> 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
>
