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.

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

NEXUS Repository Manager EOL support #4338

Open
gabriel0 opened this issue Dec 20, 2023 · 3 comments · May be fixed by #4394
Open

NEXUS Repository Manager EOL support #4338

gabriel0 opened this issue Dec 20, 2023 · 3 comments · May be fixed by #4394
Labels
bug Something isn't working

Comments

@gabriel0
Copy link

Link to product page on endoflife.date

https://endoflife.date/nexus

Details of incorrect and correct details you have found

The active support date on endoflife.date is not the same as in the product documentation.

endoflife.date: Only the latest version of each major release is supported

Product documentation:
Sonatype Nexus Repository releases are considered generally available and fully supported for a term of 1 year after the version's release date.
At that point, Sonatype provides extended maintenance for each Sonatype Nexus Repository version for an additional 6 months before that version is considered sunset.

What is the source website for the product and for its version information?

https://help.sonatype.com/docs/sonatype-sunsetting-information/sonatype-nexus-repository-3-versions-status

Additional context

image

@gabriel0 gabriel0 added the bug Something isn't working label Dec 20, 2023
Copy link

welcome bot commented Dec 20, 2023

Thank you for opening your first issue here 👍. Be sure to follow the issue template if you chose one.

@marcwrobel
Copy link
Member

Looks like the support policy were either updated, or not well documented from the beginning. Thanks for this information @gabriel0, we will update it soon.

@romainx
Copy link
Contributor

romainx commented Dec 26, 2023

Hello it seems that the cycles defined in eol, only major versions (2 and 3), do not have the same granularity as in the product documentation that indicates lifecycle for minor versions (3.62).
Should we redefine completely the cycles to match the product?

@romainx romainx linked a pull request Dec 28, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants