Simply to avoid possible regressions. As we have now some end users who
are going to test the M6, it is better to do some validation and focus
on fixing bugs to provide a good delivery. By experience, when adding
new features, especially transveral features, there are great chances
that it breaks some other parts of the tool (it was the cas for M5 with
some commits on the composite that broke IBD 2 days before the planned
delivery). We would like to avoid this situation and suggest not to
commit features during validation. But there can be exceptions if they
are limited and explained ;-)
Why the full week? simply because validation takes time and fixing bugs
too. After fixing bugs we need to validate again and we need at least 3
to 4 days for that, and one last day for final packaging and ultimate
validation on the final packaging.
Hope it helps
regards
raphaël
GERARD Sebastien 166342 a écrit :
Why stopping for a full week?
Dr. Sébastien Gérard
Head of MDD for DRES research project
CEA, LIST/LISE
Boîte courrier 94, GIF SUR YVETTE
CEDEX, F-91191 France
Phone/fax : +33 1 69 08 58 24 / 83 95
Leader of the Eclipse Component Papyrus (The UML2 Graphical Modeler): www.papyrusuml.org
http://www.eclipse.org/modeling/mdt/?project=papyrus
Before printing, think about the environment
-----Message d'origine-----
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Thibault LANDRE
Envoyé : vendredi 12 mars 2010 16:29
À : Papyrus Project list
Objet : [mdt-papyrus.dev] Helios M6 - Validation
Hi all,
Helios M6 is planned for the end of next week (19th March).
In order to validate this version, it would be great if you could limit
the number of commits next week, and don't commit enhancement.
This version will be the version tested by the community after the
presentation made at EclipseCon.
Best 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
|
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. |
|