Rudder versions look like X.Y.Z (for example, 4.1.2).
- Z version increments (X.Y.Z1 –> X.Y.Z2, for example 4.1.2 to 4.1.3) are minor bug fix only releases. They can be considered as stable as the previous release, as we make a lot of effort to reduce the amount of changes that go into these versions. A full changelog is always available. Upgrading your Rudder version to the latest minor release is always recommended, and is designed to be easy. They are released every few weeks.
- Y or X version increments are major releases. These versions include new features, and the amount of changed code can be considerable. An upgrade path from one major version to next will always be provided, but may not be between two non-consecutive versions (ie, upgrading from 3.0.* to 3.1.* is supported, and from 3.1.* to 3.2.* is too, but upgrading directly from 3.0.* to 3.2.* may not be – check the Upgrading section of the User Manual for specifics). They are released every few months.
A maintained version is a major version for which we release minor bug fix releases and communicate about security vulnerabilities.
- Our general support policy is to maintain major releases until 3 months after the next major version is released to give some time for upgrading.
- We also provide a more conservative life-cycle through ESR versions. The ESR tag is given to a major release once it has been thoroughly tested and proven reliable on real production systems. ESR versions are maintained until 6 months after the next ESR version is announced, allowing less frequent major upgrades, and a larger time-frame for switching between them.
You can subscribe to the rudder-announce mailing-list to receive release and end of life announcements. Here is a table of all versions of Rudder, their status, release dates and planned maintenance termination date:
|Version||Status||Release date||Maintained until|
||As yet unknown (at least 3 months from following version)|
||As yet unknown (at least 6 months from following ESR version)|
|4.0||End of life
||Ended 30th June 2017
|3.2||End of life||January 2016||Ended 10th February 2017|
|3.1 ESR||Maintained - planned EOL||July 2015||22th December 2017|
|3.0||End of life||February 2015||Ended 10th June 2016|
|2.11 ESR||End of life
||July 2014||Ended 10th September 2016
|2.10||End of life||March 2014||Ended 10th December 2015|
|2.9||End of life||December 2013||Ended 30th June 2014
|2.8||End of life||November 2013||Ended 31st March 2014|
|2.7||End of life||July 2013
||Ended February 2014|
|2.6||End of life||April 2013
||Ended 16th December 2014|
|2.5||End of life||January 2013
||Ended July 2013|
|2.4||End of life||December 2012
||Ended January 2014|
|2.3||End of life||October 2011
||Ended June 2013|
Customer support service by UserEcho