What our Product Release and Maintenance Policy means to the community

Hey Everyone,

In this post, we want to explain what the Product Release and Maintenance Policy means for our community and why an End of Life (EoL) process is important for open-source software as it ultimately helps you to innovate continuously. We are posting this because we recently introduced our Product Release and Maintenance Policy.

Naturally, open-source projects need to evolve and adapt according to their dependencies and contributions. EoL makes it easier to have the foresight of the product cycle and plan a smooth transition into the next phase of development. Our EoL policy defines how long a given release will be supported and how long a release is still in active development or maintenance.

”The EoL process guides the final business operations associated with a Rasa product, service, or subscription life cycle. It consists of a series of technical and business milestones and activities that, once completed, make a product, service, or subscription obsolete.” That means at the EoL, the product, service, or subscription is not sold, improved, maintained, or supported any longer.

Our goal for Rasa Open Source community users is to maintain the most recent minor release from the current major release stream. Let’s take a current example: For the Rasa Open Source 3.2.4 release, 3.2 is the minor of the 3.0 major release, which will be maintained. This allows these users to obtain packaged fixes on the latest branch while making only minor changes to their running software. Kindly refer to the references to know more about versioning, release frequency, and maintenance table.