Rudder versions

Rudder versioning

Rudder versions look like X.Y.Z (for example, 5.0.2):

  • Z version increments (X.Y.Z1X.Y.Z2, for example 5.0.2 to 5.0.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 4.1 to 4.2 is supported, and from 4.2 to 4.3 is too, but upgrading directly from 4.1 to 4.3 may not be – check the upgrade section of the user manual for specifics). They are released every few months.

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~betaN where 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~rcN where 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 maintain major releases until 3 months after the next 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 versions, with a minimal upgrade window of 6 to 9 months. You can read more about it on the subscription page.

Note: The ESR tag was previously given to major releases that were maintained 6 months after the next ESR version was announced. Rudder 4.1 is the last ESR release, extended maintenance is now provided as part of Rudder subscription.

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
Rudder 7.2.1

changelogdocs
rpmaptsources
nightly: rpmaptsources

7.1

Maintained
⇒ until 2022-12-28

2022-04-25

2022-10-12
Rudder 7.1.7

changelogdocs
rpmaptsources
nightly: rpmaptsources

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.
Rudder 7.0.9

changelogdocs
rpmaptsources

6.2

End of life

2020-12-10

2022-10-12
Rudder 6.2.20

changelogdocs
rpmaptsources

6.1

End of life

2020-06-17

2022-06-28
Rudder 6.1.21

changelogdocs
rpmaptsources

6.0

End of life

2019-12-09

2020-10-29
Rudder 6.0.10

changelogdocs
rpmaptsources

5.0

End of life

2018-09-26

2020-10-29
Rudder 5.0.20

changelogdocs
rpmaptsources

4.3

End of life

2018-04-19

2019-07-08
Rudder 4.3.14

changelogdocs
rpmaptsources

4.2

End of life

2017-09-30

2018-07-18
Rudder 4.2.7

changelogdocs
rpmaptsources

4.1

End of life

2017-03-30

2019-07-08
Rudder 4.1.24

changelogdocs
rpmaptsources

4.0

End of life

2016-11-10

2017-06-22
Rudder 4.0.7

changelogdocs
rpmaptsources

3.2

End of life

2016-01-22

2017-02-20
Rudder 3.2.11

changelogdocs
rpmaptsources

3.1

End of life

2015-07-09

2017-12-11
Rudder 3.1.25

changelogdocs
rpmaptsources

3.0

End of life

2015-02-16

2016-06-08
Rudder 3.0.17

changelogdocs
rpmaptsources

2.11

End of life

2014-07-17

2016-08-30
Rudder 2.11.24

changelogdocs
rpmaptsources

2.10

End of life

2014-03-28

2015-12-16
Rudder 2.10.20

changelogdocs
rpmaptsources

2.9

End of life

2013-12-31

2014-06-27
Rudder 2.9.7

changelogdocs
rpmaptsources

2.8

End of life

2013-11-07

2014-03-14
Rudder 2.8.4

changelogdocs
rpmaptsources

2.7

End of life

2013-07-31

2014-02-07
Rudder 2.7.8

changelogdocs
rpmaptsources

2.6

End of life

2013-04-30

2014-12-16
Rudder 2.6.20

changelogdocs
rpmaptsources

2.5

End of life

2013-01-30

2013-07-31
Rudder 2.5.6

changelogdocs
rpmaptsources

2.4

End of life

2012-12-14

2014-01-26
Rudder 2.4.13

changelogdocs
rpmaptsources

2.3

End of life

2011-10-31

2013-06-06
Rudder 2.3.13

changelogdocs
rpmaptsources


← Rudder components Compatible OS →