Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[DOCS] LTS Documentation has contradictory timeline #28135

Closed
captn3m0 opened this issue Aug 21, 2024 · 1 comment · Fixed by #28424
Closed

[DOCS] LTS Documentation has contradictory timeline #28135

captn3m0 opened this issue Aug 21, 2024 · 1 comment · Fixed by #28424
Assignees
@schavis
Labels
docs

Comments

@captn3m0
Copy link

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.

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".
captn3m0 added a commit to endoflife-date/endoflife.date that referenced this issue Aug 21, 2024
@captn3m0
[vault] Document LTS releases
03a9e86 
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.
@captn3m0 captn3m0 mentioned this issue Aug 21, 2024
Merged
hebbet pushed a commit to endoflife-date/endoflife.date that referenced this issue Aug 21, 2024
@captn3m0
[vault] Document LTS releases (#5717)
23b079f 
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.
@VioletHynes
Copy link
Contributor

VioletHynes commented Sep 17, 2024 •
edited
Loading

Hey there, thanks for noting this. I've chatted internally to confirm and your intuition is right, it's three releases, so approximately a year. Going to raise a PR to address this inaccuracy, and hopefully close this soon.

@VioletHynes VioletHynes mentioned this issue Sep 17, 2024
Merged
6 tasks
captn3m0 added a commit to endoflife-date/endoflife.date that referenced this issue Sep 18, 2024
@captn3m0
[vault] Switch to N-2 policy for LTS
bd6bd05 
As confirmed at hashicorp/vault#28135 (comment),

The official policy is N-2, and the additional year 
of support is approximate.
@captn3m0 captn3m0 mentioned this issue Sep 18, 2024
Merged
marcwrobel pushed a commit to endoflife-date/endoflife.date that referenced this issue Sep 23, 2024
@captn3m0
[vault] Switch to N-2 policy for LTS (#5859)
853e90c 
As confirmed at hashicorp/vault#28135 (comment), the official policy is N-2, and the additional year of support is approximate.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@schavis schavis

Labels
docs
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update LTS language to not contradict hashicorp/vault
4 participants
@captn3m0 @VioletHynes @schavis @heatherezell