meta data for this page
|19.3||STABLE||Matrix||GXL||S805X, S805Y, S905X, S905D, S905L, S905M2, S905W|
|19.4 RC2||RC||Matrix||GXL||S805X, S805Y, S905X, S905D, S905L, S905M2, S905W|
CoreELEC Development Cycle
The CoreELEC Development Cycle (CEDC) is defined by an Agile Methodology with clearly outlined processes for creating high-quality software.
The CEDC methodology focuses on the following phases of software development:
|Alpha(α)||■||This is the first phase of software development and testing. In this phase, a team of developers writes and tests the software, while additional validation performed by another team. Alpha software is not thoroughly tested, contains serious bugs, are generally unsuitable for the public and considered highly unstable.|
|Beta(β)||■||The next phase, β, begins when the software is feature complete but likely to still contain a significant number of bugs. In this phase, β-testers work closely together with the developers to fix the bugs. These releases are considered unsuitable for daily use.|
|RC||■||A release candidate (RC) is a β-version which has been thoroughly tested and has the potential to be a stable product. Unless significant bugs emerge, the product is considered safe for use with the public.|
|Stable||■||Also called Production Release, is the last release candidate (RC) which has passed all verifications and tests. The product is now a stable public release and considered safe to use.|
|Nightly||■||A nightly (or daily) build contains the latest version of CoreELEC, based on end-user feedback. Nightly builds include the latest security updates, features, and bug fixes. They are available to the public. These builds are considered safe to use.|
Release to The Web
CoreELEC is distributed as Release to The Web (RTW) or Web Release, a means of software delivery that utilizes the Internet for distribution. No physical media are produced by Team CoreELEC with this type of release mechanism.
During the products supported lifetime, CoreELEC is issued service releases, patches and/or updates.
Service releases contain a collection of updates, fixes, and enhancements, delivered in the form of a single package. These releases may also implement new features.
For various reasons, products will eventually reach their natural End-of-Life (EOL).
Reasons include newer and better technologies being made available, marketplace changes, or source parts and technologies no longer being available. This phase is part of any technology product lifecycle.
In this phase, development ceases, and Team CoreELEC no longer provides technical support for the product.
Team CoreELEC tries to make the EOL process as seamless as possible for end-users and partners alike, while providing transparency into what can be expected.
Service announcements are released prior to the products End-of-Life date.