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.
Difference between revisions of "Equinox/p2/Maintenance process"
(New page: This document describes the process used by the p2 team to contribute bug fixes to a maintenance stream. * Create a new bug as clone of the original one * Set the target milestone * Get c...) |
|||
| Line 8: | Line 8: | ||
* Release patch | * Release patch | ||
* Tag (or get someone to tag) | * Tag (or get someone to tag) | ||
| + | |||
| + | [[Category:Equinox_p2]] | ||
Revision as of 08:03, 3 August 2009
This document describes the process used by the p2 team to contribute bug fixes to a maintenance stream.
- Create a new bug as clone of the original one
- Set the target milestone
- Get consent from component lead (this can happen before or while the patch is written)
- Attach the patch (note that the patch in the maintenance stream does not have to be the same one than in HEAD). It is also a good practice to have released in HEAD the changes before putting it in the M build.
- Get patch reviewed
- Release patch
- Tag (or get someone to tag)