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

Papyrus/Papyrus Developer Guide/Papyrus development plan

< Papyrus‎ | Papyrus Developer Guide
Revision as of 09:52, 11 August 2009 by Thibault.landre.atosorigin.com (Talk | contribs) (New page: = Release plan for Helios = To be defined : planning migration to Helios = Milestone delivery = == from M1 to M5<br> == Adding new features and bugs fixes.<br> {| cellspac...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Release plan for Helios

To be defined :

planning

migration to Helios

Milestone delivery

from M1 to M5

Adding new features and bugs fixes.

2 weeks before - Stabilization
Freeze enhancement

Announce on mdt papyrus devel ML, enhancement freeze. The mail must specify all the key date for this release. The mail also contains the list of tasks fixed for this release.

Creating a branch (optional)

A branch is created on the repository for new development purpose. Fix of found defects are done on the head of the repository.

Validation
A first validation is done, tasks are updated according to the result of the validation.
Stabilize
Prior to new development, fix defects found during the validation (if possible). Update the relative task.
One week before - Validation

from M5 to M7

Only bugs fix. Breaking API and adding new features is not allowed.


from M7 to final release

Back to the top