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.
MDT/Papyrus/Developer Guide/Charter
< MDT | Papyrus | Developer Guide
Revision as of 10:52, 24 June 2020 by Vincent.lorenzo.cea.fr (Talk | contribs)
This is a work in progress document.
Contents
Management of service release
- M3+
It is forbidden to modify the GUI. Only important bug fixes should be merged. Creation of a branch (tag) for the release
- RC1+
Its forbidden to merge contribution. Only by the project Chief for critical bugs.
Bug Management
- When a bug is resolved the Target Milestone must be filled. For example the bug has been fixed for the service release 3 of oxygen, the target milestone is 3.3.
Papyrus Architecture
Papyrus Plugin Naming Scheme and Folders Structure
- Papyrus plugins naming scheme and folder structure used to locate and name plugins is described here: Papyrus/Papyrus_Developer_Guide/Papyrus_Plugin_Naming_Scheme
Code convention
- All instructions can be seen here
CQ
- Remember to check on the current CQs to see if they are still current and that we will not miss any currently required dependencies (e.g. glazed lists in the new orbit or the new apache.common.io dependency) as well as the IPlogs. A quick tutorial on CQs can be found here.