Views
Release Engineering/Milestones
From MeeGo wiki
< Release Engineering(Difference between revisions)
m (Draft) |
(categorise) |
||
| (One intermediate revision not shown) | |||
| Line 1: | Line 1: | ||
| - | [[File:MeeGoReleaseTimeline.JPG| | + | [[File:MeeGoReleaseTimeline.JPG|600px]] |
= MeeGo Development Milestones = | = MeeGo Development Milestones = | ||
== MM0 == | == MM0 == | ||
| + | |||
| + | '''Definition: MM0 - Concept for release done''' | ||
| + | * High level release concept defined | ||
| + | * This milestone opens active planning phase | ||
== MM1 == | == MM1 == | ||
| + | |||
| + | '''Definition: MM1 - All planning done and development started''' | ||
| + | * All planning steps done | ||
| + | ** input from customers taken | ||
| + | ** features defined | ||
| + | ** release and testing plans exists | ||
| + | ** risks identified | ||
| + | * development branch started | ||
== MM2 == | == MM2 == | ||
| + | |||
| + | '''Definition: MM2 - Intrusive changes phase completed''' | ||
| + | * All significant changes integrated | ||
| + | ** High risk items | ||
| + | ** High priority items | ||
| + | * Main Data flows verified | ||
| + | * Main performance gaps identified | ||
| + | * Environment stable for development of feature with medium/low risks | ||
| + | * Translations: code scans | ||
== MM3 == | == MM3 == | ||
| + | |||
| + | '''Definition: MM3 - Feature development phase completed''' | ||
| + | * All planned features integrated | ||
| + | ** Medium and low risk items | ||
| + | ** Lower priority items | ||
| + | * All Data flows verified from UX | ||
| + | * Reliability gaps identified | ||
| + | * Development focus switched from introducing new features to fixing bugs | ||
| + | * Translations done | ||
== MM4 == | == MM4 == | ||
| + | |||
| + | '''Definition: MM4 - Stabilization phase completed: | ||
| + | * No major and critical bugs present | ||
| + | * Moderate amount of normal and minor bugs present | ||
| + | * All features verified on all target HW | ||
| + | * No major performance or reliability issues open | ||
| + | * First release candidate created | ||
| + | * Strict change control towards release | ||
| + | * Translations finalized (no bugs open) | ||
| + | * Preparation of release announcements and marketing materials | ||
== MM5 == | == MM5 == | ||
| + | |||
| + | '''Definition: MM5 - Public MeeGo Release''' | ||
| + | * Release blockers resolved | ||
| + | * All features functional | ||
| + | * Reliability targets achieved | ||
| + | * Performance targets achieved | ||
| + | * Marketing materials and announcements ready | ||
| + | * MeeGo Release is created and published | ||
== MM6 == | == MM6 == | ||
| + | |||
| + | '''Definition: MM6 - End of active Maintenance''' | ||
| + | * We stop producing updates unless it’s really something important | ||
== MM7 == | == MM7 == | ||
| + | |||
| + | '''Definition: MM7 - End of lifecycle''' | ||
| + | * No work for that release anymore | ||
= Optional Milestones and checkpoints = | = Optional Milestones and checkpoints = | ||
== MM2.5 == | == MM2.5 == | ||
| + | |||
| + | '''Definition: MM2.5 - checkpoint for features with medium risks''' | ||
| + | * Rationale – review point to predict better MM3 state | ||
== MM3.5 == | == MM3.5 == | ||
| + | |||
| + | '''Definition: MM3.5 - checkpoint for bugfixing''' | ||
| + | * Rationale – review point of feasibility to fix all important bugs in time | ||
| + | * Might be used also for translations and user guide documentation status check | ||
== MM5.x == | == MM5.x == | ||
| + | |||
| + | '''Definition: MM5.1, MM5.2, MM5.3,... - Update releases, if needed.''' | ||
| + | * Rationale – it might be scenarios where some new features from next releases are backported to maintenance releases. | ||
| + | |||
| + | [[Category:Release engineering]] | ||
Latest revision as of 11:54, 12 April 2011
Contents |
MeeGo Development Milestones
MM0
Definition: MM0 - Concept for release done
- High level release concept defined
- This milestone opens active planning phase
MM1
Definition: MM1 - All planning done and development started
- All planning steps done
- input from customers taken
- features defined
- release and testing plans exists
- risks identified
- development branch started
MM2
Definition: MM2 - Intrusive changes phase completed
- All significant changes integrated
- High risk items
- High priority items
- Main Data flows verified
- Main performance gaps identified
- Environment stable for development of feature with medium/low risks
- Translations: code scans
MM3
Definition: MM3 - Feature development phase completed
- All planned features integrated
- Medium and low risk items
- Lower priority items
- All Data flows verified from UX
- Reliability gaps identified
- Development focus switched from introducing new features to fixing bugs
- Translations done
MM4
Definition: MM4 - Stabilization phase completed:
- No major and critical bugs present
- Moderate amount of normal and minor bugs present
- All features verified on all target HW
- No major performance or reliability issues open
- First release candidate created
- Strict change control towards release
- Translations finalized (no bugs open)
- Preparation of release announcements and marketing materials
MM5
Definition: MM5 - Public MeeGo Release
- Release blockers resolved
- All features functional
- Reliability targets achieved
- Performance targets achieved
- Marketing materials and announcements ready
- MeeGo Release is created and published
MM6
Definition: MM6 - End of active Maintenance
- We stop producing updates unless it’s really something important
MM7
Definition: MM7 - End of lifecycle
- No work for that release anymore
Optional Milestones and checkpoints
MM2.5
Definition: MM2.5 - checkpoint for features with medium risks
- Rationale – review point to predict better MM3 state
MM3.5
Definition: MM3.5 - checkpoint for bugfixing
- Rationale – review point of feasibility to fix all important bugs in time
- Might be used also for translations and user guide documentation status check
MM5.x
Definition: MM5.1, MM5.2, MM5.3,... - Update releases, if needed.
- Rationale – it might be scenarios where some new features from next releases are backported to maintenance releases.