| RE: [mdt-papyrus.dev] Minutes of the meeting 2009 09 15 |
|
Thanks. De :
mdt-papyrus.dev-bounces@xxxxxxxxxxx
[mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De
la part de Kenn Hussey Sebastien, Details on the required format for the plan can be found at http://wiki.eclipse.org/Development_Resources/Project_Plan.
As you'll see, the content is driven from/by Bugzilla, so much of the work in
putting together the plan actually involves modifying bugs. For examples of
what the completed template should look like, please see last year's MDT plan (http://www.eclipse.org/projects/project-plan.php?projectid=modeling.mdt)
and, in particular, the "sub-plans" to which it links (i.e., for each
of the sub-projects). I hope to create a "rolled up" plan for MDT
Helios as a whole again this year... Cheers, Kenn On Wed, Sep 16, 2009 at 10:25 AM, GERARD Sebastien 166342 <Sebastien.GERARD@xxxxxx> wrote: Hi all, I propose to discuss this point within next
Monday meeting. BTW, can someone send me a template of what
should look like our plan? I will draft it. Thanks, Sébastien. De : mdt-papyrus.dev-bounces@xxxxxxxxxxx
[mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de Kenn Hussey
Raphaël, To
participate in the release train, a project must synchronize its milestones
with the other projects on the train no later than M4 (i.e., December 16 for
Papyrus), so technically there's no requirement for the M2 and M3 milestones of
Papyrus to align with those of Helios. However, one of the main
objectives/benefits of the release train is "continuous integration",
so the sooner Papyrus can align with the other projects, the better, IMHO. Cheers, Kenn On Wed,
Sep 16, 2009 at 6:17 AM, Raphael FAUDOU <raphael.faudou@xxxxxxxxxxxxxx>
wrote: Hi Kenn, Thibault,
Thanks
for this. Given that the deadline for Helios project plans is the end of
September (i.e., in just two weeks), I'm concerned that we're focused on
planning only M2 and that the next meeting isn't until September 28. I would
suggest a more active approach to planning over the next couple of weeks. If we're
serious about the possibility of using an agile approach (like Scrum), I think
we need to be more aggressive about identifying all of the features that we
want to target for Helios, earmarking them for appropriate milestones (and
dates - note that the deadline for Helios M2 is September 30 rather than
October 23), and planning to meet regularly (e.g., every two weeks) to review
and adjust the plan accordingly. I'm sorry
for being so insistent on this, but I think we all want this project to be
successful. I have some available time over the next couple of weeks and would
be willing/able to help in any way I can... Cheers, Kenn 2009/9/15
Thibault LANDRE <thibault.landre@xxxxxxxxxxxxxx> Hi,
_______________________________________________mdt-papyrus.dev mailing listmdt-papyrus.dev@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev --
| |||||
