EOL.WikiEOL.Wiki
← ← Back to all products

Redmine

Active
Tools & MonitoringLatest Version: 7.0.0Latest Release: Jun 30, 2026

Redmine is a flexible open-source project management and issue tracking web application.

Support summary

Redmine currently has supported cycles. Track the next EOL date and validate upgrades before your change window.

What do EOL and support statuses mean?

Next EOL

No announced EOL date is currently listed.

Supported cycles

3

0 lts

Versions

8

Latest Version

7.0.0

Active Support

3

EOL

5

Lifecycle Timeline

Today
7.0
7.0
6.1
6.1
6.0
6.0
5.1
5.1
5.0
5.0
4.2
4.2
4.1
4.1
4.0
4.0
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
7.0Jun 30, 2026YesNo7.0.0No
Active
6.1Sep 21, 2025YesNo6.1.3No
Active
6.0Nov 10, 2024YesNo6.0.10No
Active
5.1Oct 31, 2023NoJun 30, 20265.1.13No
EOL
5.0Mar 28, 2022NoSep 21, 20255.0.14No
EOL
4.2Mar 28, 2021NoOct 31, 20234.2.11No
EOL
4.1Dec 20, 2019NoMar 28, 20224.1.7No
EOL
4.0Dec 9, 2018NoApr 26, 20214.0.9No
EOL

Data sources

Frequently Asked Questions

Which versions of Redmine have reached end of life?
The following Redmine versions have reached end of life and no longer receive security updates: 5.1, 5.0, 4.2, 4.1, 4.0. It is recommended to upgrade to a supported version.
Is it safe to continue using Redmine 5.1?
Redmine 5.1 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Redmine?
The latest version of Redmine is 7.0.0, released in the 7.0 release cycle.
How many versions of Redmine are currently supported?
Redmine currently has 3 actively supported version(s): 7.0, 6.1, 6.0.
When does Redmine 7.0 reach end of life?
Redmine 7.0 does not have a specific end-of-life date announced yet.
What should I do when Redmine reaches end of life?
When a Redmine version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.