Home | Sitemap | Contact Us | Ordering

Champion Release Cycle

Champion (Atlantis/Daedilus) Release Cycle

Champion CMS is a volunteer effort, as you know, so it is difficult to set dates for releases. We set targets that we would like to achieve but as our workload varies depending on the complexity of the changes we have set in our goals and as our resources change depending on the availability of team members, any dates we set can be indicative only.

Development Releases

Release type	Development target	Cycle (approx)	Backward compatibility	Support	Repository
Major (1.2.3)	Focuses on major code refactoring. Public testing phase is used.	12 months	May break backward compatibility with previous major version.	Support ends 12-18 months after the next major release.	Development is done in separate branches, and is merged later on with the trunk.
Minor (1.2.3)	Provides additional features and improved functionality. No major rewrites.	4 months	Holds 80%-100% backward compatibility with previous version.	Support ends when next minor version is declared stable.	Development is done in a separate branch holding the new minor release identification.

Maintenance Releases

Maintenance releases are updates to minor versions of Champion. No new features are added. These releases are for fixing bugs and usability issues that have been identified in the previous release and are also used for security updates.

Release type	Development target	Cycle	Backward compatibility	Support	Repository
Maintenance (1.2.3)	Maintenance Releases aim to improve the quality of stable releases by fixing bugs. Also used for closing security vulnerabilities.	As required.	Holds 100% backward compatibility with previous minor - and maintenance versions.	Support ends when next release is declared stable.	Development is done in a separate branch holding minor release number. After release it is merged into the trunk for the active trunk version.

Champion (Prometheus) Release Cycle

Development Releases

Release type	Development target	Cycle (approx)	Backward compatibility	Support	Repository
Major (Year)	Focuses on major code refactoring. Public testing phase is used.	12 months	May break backward compatibility with previous major version.	Support ends 12-18 months after the next major release.	Development is done in separate branches, and is merged later on with the trunk.
Minor (year.x.x)	Provides additional features and improved functionality. No major rewrites.	6 months	Holds 80%-100% backward compatibility with previous version.	Support ends when next minor version is declared stable.	Development is done in a separate branch holding the new minor release identification.

Maintenance Releases

Release type	Development target	Cycle	Backward compatibility	Support	Repository
Maintenance (year.x.x)	Maintenance Releases aim to improve the quality of stable releases by fixing bugs. Also used for closing security vulnerabilities.	As required.	Holds 100% backward compatibility with previous minor - and maintenance versions.	Support ends when next release is declared stable.	Development is done in a separate branch holding minor release number. After release it is merged into the trunk for the active trunk version.

Home Services Blogs Sitemap

Syndicate

You are here :

Unparalleled Support

Hours of Operation: 24/7/365
For all technical support related question and issues.

To get technical assistance for your any of your Hosting plans.
These include Reseller, VPS, Semi-dedicated and Dedicated plans.
• Linux Support

To get technical assistance for your Windows® hosting plans.
• Windows® Support

To contact the support manager:
• Support Manager

Why Choose Us!

- Unparalleled Support

- 30-Day Money Back Guarantee

- Award Winning Tech Support

- Best pricing in Hosting Industry

- We offer a broad range of web hosting services to meet the needs of our diverse portfolio of clients

- Our our services are backed by 24/7 professional customer support, stellar hardware, money back guarantee, and uptime guarantee.