Re: [mdt-papyrus.dev] Update of the project plan for Papyrus Neon

[Christian Damus <give.a.damus@xxxxxxxxx>]

Hi, Rémi,

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.

Cheers,

Christian

On 10 March, 2016 at 09:11:29, SCHNEKENBURGER Remi 211865 (remi.schnekenburger@xxxxxx) wrote:

Dear committers,

 

Current release plan for version 2.0.0 is accessible here[1]. It is filled up with some queries based on a given set of keywords. So, in order to have a clear public roadmap, some bugs considered as being part of the Papyrus plan should be updated.

 

I prepared a small wiki page [2] to describe the various properties a bug should have to be part of the release plan. In case of top level bugs, as for example the Papyrus 2.0 bundle refactoring bug[3], only the top level one should be updated, in order to keep a clear and readable roadmap.

 

To each committer in charge of eligible bugs, please update them.

 

Best regards,

Rémi

 

[1]  https://projects.eclipse.org/projects/modeling.mdt.papyrus/releases/2.0.0/plan

[2] https://wiki.eclipse.org/Papyrus_Developer_Guide/Contributing_To_Release_Plan

[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220

 

-------------------------------------------------------

 

Rémi SCHNEKENBURGER

+33 (0)1 69 08 48 48

CEA Saclay Nano-INNOV

Institut CARNOT CEA LIST

 

www.eclipse.org/papyrus

 

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev