Re: [mdt-papyrus.dev] Minutes of the meeting 2009 09 15

[Kenn Hussey <kenn.hussey@xxxxxxxxx>]

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
Envoyé : mercredi 16 septembre 2009 15:31
À : raphael.faudou@xxxxxxxxxxxxxx; Papyrus Project list

Objet : Re: [mdt-papyrus.dev] Minutes of the meeting 2009 09 15

 

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,

in the case we want to catch the Helios Train, is it mandatory that we stick now to Helios M2 or can we wait one month more to branch the backbone on M2?
By sticking to M2 milestone, we get the risk to get an unstable Helios platform and to consume time in finding bugs coming from this platform and in updating our environement oftenr. In addition we take the risk to limit the experiments in our companies in the next months (people want to test MDT Papyrus on their Eclipse Galileo environment).
What is your opinion about it?
thanks
raphaël

Kenn Hussey a écrit :

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,

here is the minutes of yesterday's meeting.

Regards,

Thibault

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev

 

_______________________________________________

mdt-papyrus.dev mailing list

mdt-papyrus.dev@xxxxxxxxxxx

https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev

 

--

	Raphaël FAUDOU Responsable cellule Innovation / bureau méthodes Head of Innovation & Method Definition Embedded systems & critical systems Atos Origin Tel     : +33 (0)5 34 36 32 89 Tel     : +33 (0)6 10 53 50 44 Mail   : raphael.faudou@xxxxxxxxxxxxxx
Atos Origin 6, Impasse Alice Guy BP 43045 31024 Toulouse Cedex 3, France

P Avant d'imprimer cet e-mail, pensez à l'environnement. Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.
P Please consider your environmental responsibility before printing this e-mail. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev

 

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev