Looking for to create a support ticket? If you’ve already created one, here’s some helpful information our RackN release policies.
We track release notes for all releases with our regular documentation.
Updated January 2022
|Release||Date||Support Level||UX Enabled||Expected End of Life|
|v3.x||None||No||n/a (past EoL)|
|v4.0||Aug 2019||None||Yes||August 2020|
|v4.1||Oct 2019||None||Yes||October 2020|
|v4.2||Dec 2019||None||Yes||December 2020|
|v4.3||June 2020||Critical||Yes||February 2021|
|v4.4||July 2020||Critical||Yes||April 2021|
|v4.5||Sept 2020||Critical||Yes||December 2021|
|v4.6||Feb 2021||Critical / Urgent||Yes||June 2022|
|v4.7||May 2021||Critical / Urgent / Normal||Yes||December 2022|
|v4.8||Nov 2021||Critical / Urgent / Normal||Yes||June 2023|
|v4.9||Feb 2022||Full – Current||Yes||December 2023|
End of Maintenance Schedule
RackN follows an End of Maintenance Schedule for each release. A release is a change to the major or minor version.
If an Urgent or lower fix is already available in an existing minor release, customers are expected to migrate to the newer minor release.
|Immediately After Release||Yes||Yes||Yes||On Review|
|After Next Release||Yes||Yes||On Review||No|
|After Two Newer ReleasesOr at most 6 months After||Yes||Yes||No||No|
|After Three Newer ReleasesOr at most 12 months After||Yes||No||No||No|
|After Four Newer ReleasesOr at most 18 months After||End of Maintenance|