Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] [PROVENANCE INTERNET] Re: Update of the project plan for Papyrus Neon

No problem ;)

To all committers: Change in the instructions. Please set the flag to Neon+ in the bugs part of the plan. I will update the wiki page and the queries from the release plan.

Regards,
Remi

De : GERARD Sebastien 166342
Envoyé : ‎10/‎03/‎2016 09:46
À : Papyrus Project list
Objet : [PROVENANCE  INTERNET] Re: [mdt-papyrus.dev] Update of the project plan for Papyrus Neon

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

 

Description : PapyrusLogo_SmallFormatwww.eclipse.org/papyrus

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de GERARD Sebastien 166342
Envoyé : jeudi 10 mars 2016 09:40
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : [PROVENANCE INTERNET] Re: [mdt-papyrus.dev] Update of the project plan for Papyrus Neon

 

An alternative is to use the tag « Target Milestone » instead of “Version”.

 

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:38
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : [PROVENANCE INTERNET] Re: [mdt-papyrus.dev] Update of the project plan for Papyrus Neon

 

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

 

Description : PapyrusLogo_SmallFormatwww.eclipse.org/papyrus

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Christian Damus
Envoyé : jeudi 10 mars 2016 09:30
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : Re: [mdt-papyrus.dev] Update of the project plan for Papyrus Neon

 

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

 

Description : PapyrusLogo_SmallFormatwww.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


Back to the top