Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Papyrus/Papyrus Developer Guide/How To- Plan contribution"
(→Whiteboard) |
(→Whiteboard) |
||
Line 12: | Line 12: | ||
{| class="wikitable" | {| class="wikitable" | ||
− | | | + | !colspan="2"|Themes |
|- | |- | ||
|Whiteboard | |Whiteboard |
Revision as of 07:08, 8 December 2014
Contents
How to contribute to the release plan
Release plan is contributed through bugzilla. It is relying on a given set of queries over the bugzilla base. All items that should be part of the roadmap have to follow the following rules in order to be present in the roadmap plan.
Component
The bugs should be recorded against the MDT.Papyrus component.
Keyword
The keyword 'plan' should be set in the keyword field
Whiteboard
The bugs to build the roadmap are classified against a predefined set of themes. For the Mars version of Papyrus, the following themes are available
Themes | |
---|---|
Whiteboard | Description |
Editors | All generic features related any kind of Papyrus diagram editor |
Extensibility | Extensiblity improvements of the MDT Papyrus implementation and APIs |
Scalability | Scalability and performance improvements of the Papyrus implementation and APIs |
Usability | usability improvements of the Papyrus implementation and APIs |
Documentation | Documentation of the Papyrus implementation and APIs, user & developer aspects |
Miscellaneous | Tasks that may not be included in one of the previous theme |
Eclipse_Compatibility | Support and compatibility with platform 4.X and 3.X |