So the proposition of C. Damus seems the most adequate… (sorry ;-)
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de SCHNEKENBURGER Remi 211865
Envoyé : jeudi 10 mars 2016 15:44
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : [PROVENANCE INTERNET] Re: [mdt-papyrus.dev] Update of the project plan for Papyrus Neon
‘Target Milestone’ is supposed in this case to give a more detailed plan, with the estimated milestone on which the feature or fix will be available.
For example, the welcome page feature is available since Neon M5.
Rémi
-------------------------------------------------------
Rémi SCHNEKENBURGER
+33 (0)1 69 08 48 48
CEA Saclay Nano-INNOV
Institut CARNOT CEA LIST
www.eclipse.org/papyrus
An alternative is to use the tag « Target Milestone »
instead of “Version”.
Hi Christian,
For simplicity reasons, I prefer the version to be updated to 2.0.0 rather than setting the flag Neon+. For example, flags are not directly accessible
from the Bugzilla search web UI. You have to go to the advanced tab to have them part of the search.
Currently, the query is looking only at the given parameters in the wiki.
Regards,
Rémi
-------------------------------------------------------
Rémi SCHNEKENBURGER
+33 (0)1 69 08 48 48
CEA Saclay Nano-INNOV
Institut CARNOT CEA LIST
www.eclipse.org/papyrus
I have a question about the required bug properties. The wiki indicates that the version should be set to 2.0.0, but the version field is meant to indicate
the version in which a bug was found (or enhancement deemed to be missing). Does the query depend on the version? Perhaps it should rather look for a +neon flag, as for example the UML2 project does.
On 10 March, 2016 at 09:11:29, SCHNEKENBURGER Remi 211865 (remi.schnekenburger@xxxxxx)
wrote: