CAS EOL Policy Proposal


The CAS project management committee has been reviewing a proposal on CAS release policies, maintenance and lifetime. In particular, this proposal attempts to provide answers to the following questions:

  • How long should a CAS release be maintained?
  • What is the appropriate scope for release maintenance once a release is retired?

Today

The project has been handling release management and maintenance in a semi-official capacity. Today’s release practices typically are:

  • Patch releases, once every 30 days.
  • Minor releases, once every 3-4 months.
  • Major releases, where appropriate based on community demand and technical landscape.
  • Security patches, whenever needed and preferably as soon as humanly possible.

There is no official policy to indicate the lifespan of a CAS release. Maintaining multiple release lines in an adhoc fashion is a very time-consuming and difficult process where the development team has to ensure patches across releases are ported backward or forward correctly and that changesets are properly cherry-picked into the target release, tested, documented and made available.

This process is simply not sustainable.

Proposal

To mitigate some of this pain, the following proposal and a decidedly simple one at that is in the making:

  • CAS adopters MAY EXPECT a CAS release to be maintained for one calendar year, starting from the original release date.
  • Maintenance during this year includes bug fixes, security patches and general upkeep of the release.
  • Once the year is passed, maintenance of the release is STRICTLY limited to security patches and fixing vulnerabilities for another calendar year.
  • The lifespan of a release MAY be extended beyond a single year, to be decided by the CAS PMC and the community at large when and where reasonable.

By “CAS Release”, we mean anything that is a minor release and above. (i.e. 4.1.x, 4.2.x, 5.0.0, 5.1.0, etc).

What does this mean?

The above policy, once in effect, implies that the following CAS releases will transition into a security-patch mode (SPM) only and will be EOLed at the indicated dates.

Release SPM Starting Date Full EOL
4.0.x October 31st, 2016 October 31st, 2017
4.1.x January 31st, 2017 January 31st, 2018
4.2.x January 31st, 2017 January 31st, 2018
5.0.x September 30th, 2017 September 30th, 2018

All past releases that are absent in the above table are considered EOLed.

Misagh Moayyed

Related Posts

Apereo CAS - Extending Webflows

Learn and master extending CAS 5 Spring Webflow definitions.

Apereo CAS - Administrative Endpoints & Monitoring

Gain insight into your running Apereo CAS deployment in production. Learn how to monitor and manage the server by using HTTP endpoints and gather metrics to diagnose issues and improve performance.

Apereo CAS - Custom Authentication & Attribute Sources

Master writing custom authentication handlers/schemes in CAS and learn how to design custom data sources that can produce user claims and attributes.

Apereo CAS - User Interface Customizations

A short tutorial on Apereo CAS user interface customizations, including themes, localization and dynamic views for all those who enjoy front-end development and suffer from instant gratification.

CAS Multifactor Authentication with Google Authenticator

A short walkthrough to demonstrate how one might turn on multifactor authentication with CAS using Google Authenticator, leveraging a variety of triggers.

CAS 5.3.x Deployment - WAR Overlays

Learn how to configure and build your own CAS deployment via the WAR overlay method, get rich quickly, stay healthy indefinitely and respect family and friends in a few very easy steps.

CAS 5.3.0 RC4 Feature Release

...in which I present an overview of CAS 5.3.0 RC4 release.

Apereo CAS - Identity Impersonation

You do not always have to be you. Allow the Apereo CAS server to allow you to pretend to be another person for fun and profit.

Apereo CAS - Customized Settings

Extend the Apereo CAS server to allow custom configuration properties and settings.

Apereo CAS - Handling Multiple Logout URLs

Extend the Apereo CAS server to allow for multiple logout URLs during SLO operations.