Rework nexus repo

[romainx]

Fixes #4338

• Redefine the way versions are tracked major -> major.minor.
  Maintenance will require more work, but current data was inaccurate or even wrong.
• Use the same terminology as the vendor (extended maintenance + sunset).
• Updating the version scheme documentation to match vendor website.
• Set the Sonatype icon.

Cheers 🍰

[marcwrobel]

Thanks for this update @romainx. Following my comment on #4338 (comment) I think I remember why I only documented major versions. This is because I wanted to document the OSS version, not the commercial one.

But it would be great if we could confirm the description is still true and change it if needed. We also could document the commercial Nexus repository on a separate page.

[romainx]

Thanks for the review @marcwrobel, I've implemented the required changes.
Sorry for the V2, my bad completely forgot to take those versions into account.

For the information regarding EOL and support, according to the product download page, I would say that the information provided on the Nexus page can apply to both OSS and Pro versions. The license permits to activate features to get the Pro version.

The download is used for both Sonatype Nexus Repository Pro and OSS. See Installing and Updating Licenses for information on getting your OSS version to Pro with your professional license.

If we get a look at the Sonatype Product Development Overview where the definition of General Availability, Extended Maintenance and Sunsetted are given they also seem to be valid for both versions.

So we could turn this page into Nexus OSS / Pro in order to cover both subscription in a single page.
I've made a change on the product name to see how it could work.
What do you think?

[gabriel0]

Hi @marcwrobel @romainx , is this going to be released?

Regards in advance

[marcwrobel]

Hi @marcwrobel @romainx , is this going to be released?

Sure, I missed @romainx 's comment. I just rebased the PR and I will start another review round.

[marcwrobel]

@romainx just pushed a commit to improve automation and update releases using our automation scripts: see 84f561f.

[marcwrobel]

@romainx, sorry for the delay and thanks for the contribution. I think we're close to merging. Let me know what you think of my suggestions.

[romainx]

@marcwrobel no worries at all. Thank you for your thorough review.
I made the suggested changes. So I guess we have now the green lights to merge it.

[marcwrobel]

I made the suggested changes. So I guess we have now the green lights to merge it.

Yep, thanks again for this contribution !