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