Software Life Cycle Policy
Software
Life Cycle Policy | MPI Release
Types | MPI Version Numbering |
General Example | Branch
Example
MEI's Software Life Cycle Policy defines the scope of
feature development, release availability, and support during a product's
life span. This policy benefits customers, potential customers, partners,
VARs, and MEI. It enables interested parties to understand the maturity
levels of the various release types
and to plan for their software migration strategies.
|
Life Phase
|
Description
|
Release
Type
|
Timeline
|
Product
Sales
|
Support
|
|
Active
|
New features are designed, developed, tested,
and released |
Alpha
|
At least one of each prior to a Production
Release |
None
|
No
|
|
Beta
|
|
Production
|
Every 6-9 months |
General
Availability
|
Yes
|
|
Branch
|
As required |
Customer
Specific
|
Yes
|
|
Maintenance
|
Bug fixes only |
Patch
|
As needed
(typically every 1-2 months) |
General
Availability
|
Yes
|
|
Retirement
|
End of life |
None
|
3-4 years after Production or Branch Release |
None
|
No
|
Active
The development scope, feature requirements, and schedule are planned.
New features are designed, specified, reviewed, implemented, tested, and
documented. Early releases are made available to select customers, partners,
and VARs for feedback. After testing is complete, the release is deployed.
Maintenance
No new features are added. Bug fixes are implemented based on criticality
and availability of the next release.
Retirement
No further development or bug fixes are implemented.
See Release Types
for more details.
|
