You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a reader, reading that page, the End-of-Extended-Maintenance Date can be read two different ways:
End of Standard Maintenance + 1year
This is what the text implies.
After the first year, LTS Vault versions move from standard maintenance to extended maintenance for an additional year
End of Standard Maintenance + 3 major releases
This is what the table implies by penning down the date for 1.16 as "CY26 Q1 (1.22 release)".
While these two will likely match in normal cases, in case of a change in timeline for 1.22 (for any reason) - the dates can differ, resulting in ambiguity.
Expected behavior
The page should not have contradicting information. It might be simpler to just say "the latest 2 LTS releases are supported at any given time, following a N-1 policy. Since Vault releases 3 releases every year, this results in approximately 1 year of standard maintenance, followed by one year of extended maintenance".
The text was updated successfully, but these errors were encountered:
captn3m0
added a commit
to endoflife-date/endoflife.date
that referenced
this issue
Aug 21, 2024
Closes#5707
The policy isn't crystal clear as it mixes relative dates (3 releases forward) with absolute intervals (1 year). I've filed hashicorp/vault#28135 as a result.
Closes#5707
The policy isn't crystal clear as it mixes relative dates (3 releases forward) with absolute intervals (1 year). I've filed hashicorp/vault#28135 as a result.
Describe the bug
The end of Extended maintenance for a given LTS release is documented two different ways at https://developer.hashicorp.com/vault/docs/enterprise/lts.
For a reader, reading that page, the End-of-Extended-Maintenance Date can be read two different ways:
End of Standard Maintenance + 1year
This is what the text implies.
End of Standard Maintenance + 3 major releases
This is what the table implies by penning down the date for 1.16 as "CY26 Q1 (1.22 release)".
While these two will likely match in normal cases, in case of a change in timeline for 1.22 (for any reason) - the dates can differ, resulting in ambiguity.
Expected behavior
The page should not have contradicting information. It might be simpler to just say "the latest 2 LTS releases are supported at any given time, following a N-1 policy. Since Vault releases 3 releases every year, this results in approximately 1 year of standard maintenance, followed by one year of extended maintenance".
The text was updated successfully, but these errors were encountered: