[DOCS-11317] Minimum version of 3.0 required before upgrading to 3.2 missing on manual/release-notes/3.2-upgrade/ Created: 13/Feb/18  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Akira Kurogane Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769
Story Points: 0.3

 Description   

The minor 3.0.x version number needed before upgrading to 3.2 is absent now on the 3.2. upgrade instructions page.

There's only one spot "3.0." appears at all, and it seems the x subversion was just deleted at some point.

https://docs.mongodb.com/manual/release-notes/3.2-upgrade/#id1

My vague memory is that it should be 3.0.4, but 3.0.8 makes more sense given the release date of 3.2.0.

EOL for 3.0 is right now (end of February) so it would be helpful to get this fixed asap. I hope the value can be found in an earlier commit of the manual.



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Comment by Akira Kurogane [ 15/Feb/18 ]

Thanks Kelsey! I'm sorry I didn't figure out the right place to look in github myself.

I don't think the docs make sense as they are now however. When a user skims around they quickly get the (correct) idea that can't just upgrade from any 3.0 version. But then we're a tease and don't say what that version is. The closest we get to saying something is "latest version", in the context of coming from 2.6 first. So a worry-wort with 3.0.14 installed will feel obliged to install 3.0.15, which is a waste of their time.

I'd like to request we put the "3.0.7" back, i.e. revert the following change:

-To upgrade an existing MongoDB deployment to 3.2, you must be running 3.0.7 or later.
+To upgrade an existing MongoDB deployment to 3.2, you must be running 3.0-series release.

The advice about upgrading to the latest 3.0-series release if coming from 2.6 is good, but it shouldn't have been a reason to stop letting know existing 3.0 users that any version 3.0.7 or higher is already good enough.

Comment by Kelsey Schubert [ 14/Feb/18 ]

akira.kurogane, it was 3.0.7. Here's the commit changing the text: https://github.com/mongodb/docs/commit/1f9906b7938b7954688e69c1f53ab3e7cc9d8077#diff-0289a551d6fc55038095abceb1b1fef2

I think SERVER-20460 is the reason why we specify 3.0.7, but I could be mistaken. If that is the context, then I think the docs as they currently read make sense.

Generated at Thu Feb 08 08:02:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.