MPI Release Types
Software
Life Cycle Policy | MPI Release Types
| MPI Version Numbering
|
General Example | Branch
Example
During a general software development cycle, there are
several release types with varying maturity levels. A typical cycle begins
with several internal development builds, followed by an Alpha, Beta,
and finally a fully tested Production release. If bugs are found in the
Production release, Patch releases are issued to fix problems.
Some OEMs may have special features or schedule requirements
that do not fit into a general software development cycle. To meet these
requirements, MEI can make a Branch release from an existing Production
or Patch release. This makes it possible to add one or more features quickly,
while keeping risk low. To qualify for a Branch release, certain volume/price
requirements must be met. Contact MEI Sales for details.
|
Release
Type
|
Example
Version
|
Purpose
|
Maturity
|
Recipient
|
|
Development
|
01.02.Dev0
|
New feature devlopment |
Minimal testing, may have major defects |
MEI Only |
|
Alpha
|
01.02.Alpha0
|
Early feeedback for new features |
Feature complete and relatively stable |
Must be qualified by Engineering |
|
Beta
|
01.02.Beta0
|
Feedback and testing by Beta Program members |
Stable, but may have minor bugs |
|
Production
|
01.02.00
|
General introduction of new features |
Fully tested |
Any customer, partner, or VAR |
|
Patch
|
01.02.01
|
Fix bugs in an existing Production Release |
Field issues resolved |
Any customer, partner, or VAR |
|
Branch
|
01.02.00.b1.1
|
Add features to an existing Production or Patch release
for a specific customer |
Release specific. Dependent on scope of new features |
Must be qualified by Sales and Engineering |
Development
Internal release available for MEI purposes only.
Alpha
The release is feature complete and relatively stable. It is not completely
tested and could have major functional or design defects. Alpha releases
are given to select customers early in the debug/test phase for feedback.
Bug fixes are not provided unless they prevent evaluation. Alpha releases
are not supported or maintained.
Beta
The release is stable, but may have minor bugs. Testing is still in progress.
Beta releases are given to customers and partners late in the debug/test
phase for field test and feedback. Bug fixes are not provided. Beta releases
are not supported or maintained.
Production
A general release containing new features. The release has been fully
tested, approved by Software Quality Assurance, and the support site (http://support.motioneng.com)
has been updated. Production releases are supported and maintained with
periodic Patch releases when necessary.
Patch
A release that contains one or more bug fixes or enhancements. No major new features are implemented
in Patch releases. Typically built for a Production release. If there
is a critical bug, it can be built for a Branch.
Branch
A release that contains one or more features added to a previous Production
or Patch release. A Branch is a customer specific development. The feature
requirements, deliverables, and schedule are determined between MEI Engineering
and the customer. A Branch development cycle may or may not have Alpha
and/or Beta Branch releases. The testing and relative maturity depends
on the scope of the new features and/or changes. If bugs are found in
the field, a Patch release can be built for a Branch.
|
