Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Papyrus/Papyrus Developer Guide/Contributing To Release Plan"

(initial version of the page)
 
(Replaced content with "to be deleted")
 
(3 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== How to - Contributing to Release Plan for Neon version ==
+
to be deleted
 
+
=== Context ===
+
This page is dedicated to developers or contributors for the incoming release for Neon release train. The goal is to contribute to the release plan so the community is aware of the ongoing work and plan. The plan is build using bugzilla queries, with special tags and keywords. The developers can also identify the kind of contribution, enhancement or development of a new feature, the theme targeted by the task (usability, customizability, etc.).
+
All the content will be displayed on this page: [https://projects.eclipse.org/projects/modeling.mdt.papyrus/releases/2.0.0/plan Neon Release Plan].
+
 
+
=== Requirements ===
+
The bugs need to be in the Eclipse data base, which means the person in charge of the bug modification (keyword, tags, etc) must be an Eclipse committer or must be the initial writer of the bug.
+
 
+
=== Fill in bug information ===
+
The release plan is split in several themes:
+
* Customizability
+
* Scalability
+
* Usability
+
* Editors
+
* Documentation
+

Latest revision as of 10:50, 19 November 2020

to be deleted

Back to the top