Rudder versions
Rudder versioning
Rudder releases follow a X.Y.Z version scheme (for example, 7.1.2):
-
Xversion increments are major releases. These versions include new features and architecture changes, and the amount of modifications can be considerable. An upgrade path from one major version to the next will always be provided (i.e., upgrading from 5 to 6 is supported, and from 6 to 7 is too, but upgrading directly from 5 to 7 will generally not be – check the upgrade section of the user manual for specifics). They are released approximately every 9 to 12 months. -
Yversion increments are minor releases. These versions include small new features and various improvements, but no major change in the architecture of Rudder. An upgrade path from one minor version to the next ones (for a given major version) will be provided – check the upgrade section of the user manual for specifics). They are released every few months. -
Zversion increments are patch releases. They contains bug or security fixes, and we make a lot of effort to reduce the amount of changes that go into these version (a full change log is always available). Upgrading your Rudder version to the latest patch release is always recommended, and is designed to be easy. They are released every few weeks.
Pre-release versioning scheme
Final release just have the version described above: X.Y.Z. However before a release we have many steps.
-
alpha: only available as nightly so no versioning, expect breakage
-
beta:
X.Y.Z~betaNwhere N increments for each new beta, this is a version that builds but new feature and breakage should still be expected. -
rc:
X.Y.Z~rcNwhere N increments for each new rc, this is a version that should pass most tests and new feature should not happen anymore. -
release:
X.Y.Z̀which is the final version as described above
Nightly versioning scheme
Rudder packages are built every night. There is a nightly scheme for each release step. Note that nightly dependencies between rudder packages are less strict than release dependencies to allow installing even if some packages failed to build.
-
alpha:
X.Y.ZalphagitYYYYMMDDHHMM -
beta:
X.Y.ZbetaNgitYYYYMMDDHHMM -
rc:
X.Y.ZrcNgitYYYYMMDDHHMM -
release:
X.Y.Z~gitYYYYMMDDHHMM
Rudder life cycle
A maintained version is a major version for which we release minor bug fix releases and communicate about security vulnerabilities.
-
Our general policy is to provide patch releases for an X.Y version during at least 3 months after the next minor or major version is released to give some time for upgrading.
-
For a slower major upgrade pace, Rudder subscription provides (among other benefits) long-term maintenance of 18 to 24 months after release (depending on the subscription level) for Rudder major versions, with a minimal upgrade window of 6 to 9 months. You can read more about it on the subscription page.
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:
Versions
| Status | First release | Latest release | Links | |
|---|---|---|---|---|
→ 7.2 |
Maintained |
2022-09-28 |
2022-10-12 |
changelog ‧ docs |
→ 7.1 |
Maintained |
2022-04-25 |
2022-10-12 |
changelog ‧ docs |
7.0 |
End of life |
2022-01-27 |
Unknown internal error!
Cause: The view function did not return a valid response. The function either returned None or ended without a return statement.
Traceback (most recent call last):
File "/usr/local/release-info/release_info/views.py", line 268, in rudder_version_release_info
return format_response( last)
File "/usr/local/release-info/release_info/views.py", line 49, in format_response
response = make_response(data)
File "/usr/lib/python3/dist-packages/flask/helpers.py", line 223, in make_response
return current_app.make_response(args)
File "/usr/lib/python3/dist-packages/flask/app.py", line 2097, in make_response
raise TypeError(
TypeError: The view function did not return a valid response. The function either returned None or ended without a return statement. |
|
6.2 |
End of life |
2020-12-10 |
2022-10-12 |
|
6.1 |
End of life |
2020-06-17 |
2022-06-28 |
|
6.0 |
End of life |
2019-12-09 |
2020-10-29 |
|
5.0 |
End of life |
2018-09-26 |
2020-10-29 |
|
4.3 |
End of life |
2018-04-19 |
2019-07-08 |
|
4.2 |
End of life |
2017-09-30 |
2018-07-18 |
|
4.1 |
End of life |
2017-03-30 |
2019-07-08 |
|
4.0 |
End of life |
2016-11-10 |
2017-06-22 |
|
3.2 |
End of life |
2016-01-22 |
2017-02-20 |
|
3.1 |
End of life |
2015-07-09 |
2017-12-11 |
|
3.0 |
End of life |
2015-02-16 |
2016-06-08 |
|
2.11 |
End of life |
2014-07-17 |
2016-08-30 |
|
2.10 |
End of life |
2014-03-28 |
2015-12-16 |
|
2.9 |
End of life |
2013-12-31 |
2014-06-27 |
|
2.8 |
End of life |
2013-11-07 |
2014-03-14 |
|
2.7 |
End of life |
2013-07-31 |
2014-02-07 |
|
2.6 |
End of life |
2013-04-30 |
2014-12-16 |
|
2.5 |
End of life |
2013-01-30 |
2013-07-31 |
|
2.4 |
End of life |
2012-12-14 |
2014-01-26 |
|
2.3 |
End of life |
2011-10-31 |
2013-06-06 |
← Rudder components Compatible OS →