As we approach the release of version 11 we want to ensure that our
release process is transparent. Starting with version 11 all releases will
follow the following process.
Alpha builds are produced whenever we hit a development milestone. These
Alpha builds are for internal consumption so that the professional services
team can try functionality, provide feedback and build up best practice around
new features. We can provide demos to clients that are interested in specific
features to obtain feedback ahead of the release. This allows us to respond to
feedback and improve features. For version 11 these releases will be in the
version 10.8.x.x range.
When the test team begins their end to end regression test, the
development phase is complete. A Beta release will be made available for
clients participating in the beta program. The Beta release is supported in
development only and is not intended for production.
The MEDM team works with the client to determine the appropriateness of
inclusion in the beta program for each version. The aim of the beta phase
is to collect feedback on new features from the broader client base.
Ideal candidates would be those clients in early or active stages of
development who intend to release the version into production once it is made
generally available. Acceptance into the beta program comes with an agreement
on expectations of both MEDM and the client during the beta phase. For version
11 these releases will be in the version 10.9.x.x range.
The release is made generally available when the end to end regression
test has completed and the EDM product team has received sufficient feedback
and addressed any serious concerns from the beta clients.. This release is
represented with a version number of 11.0.0.0.
More detail of this can be found on EDM Confluence
