Versions |
Quality |
Objectives |
Time Frame |
0.8.0–0.8.x |
Alpha |
• API audit: make sure API is intuitive and consistent. Breaking the API is allowed here, but nothing should be modified too heavily as things are already fairly consistent and user friendly.
• Security audit: make sure that the code is secure and has no obvious vulnerabilities.
• Community involvement: solicit feedback from the Internet and CMS communities in order to make the Onpub code and documentation the best it can be. |
April 2007–To Be Announced |
0.9.0–0.9.x |
Beta |
• API freeze: only major bugs and/or inconsistencies in the API will be fixed during this phase of development.
• UI enhancements: the Onpub web interface will be polished to be as attractive and user friendly as possible for version 1.0. |
TBA |
1.0.0–1.x.y |
Production |
• General availability: code is robust enough to recommend for usage in production systems. At this point there should be no obvious bugs in the code.
• API stability: API is guaranteed to remain compatible with client code throughout all 1.x.y releases. |
TBA |