[DOCS-4941] Comment on: "manual/release-notes/3.0-upgrade.txt" (upgrading replica set from versions older than 2.6) Created: 08/Mar/15  Updated: 30/Oct/23  Resolved: 08/Apr/15

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

Type: Bug Priority: Major - P3
Reporter: Ernie Hershey Assignee: Allison Reinheimer Moore
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: http://docs.mongodb.org/manual/release-notes/3.0-upgrade/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.76 Safari/537.36
Referrer: http://docs.mongodb.org/manual/release-notes/3.0/
Screen Resolution: 1366 x 768
repo: docs
source: release-notes/3.0-upgrade


Participants:
Days since reply: 8 years, 45 weeks ago

 Description   

We link to the 2.6 upgrade documentation in the last bullet of this section - http://docs.mongodb.org/manual/release-notes/3.0-upgrade/#upgrade-a-replica-set-to-3-0

So it seems like we're referring to the process users should follow if they're running a version prior to 2.6 but we don't say that.

We say this:
To upgrade a replica set from MongoDB 2.6 to 3.0, upgrade all members of the replica set to version 2.6 first, and then follow the procedure to upgrade from MongoDB 2.6 to 3.0.

It should say something like:
To upgrade a replica set to 3.0 from a MongoDB version prior to 2.6, upgrade all members of the replica set to version 2.6 first, and then follow the procedure to upgrade from MongoDB 2.6 to 3.0.



 Comments   
Comment by Githook User [ 08/Apr/15 ]

Author:

{u'username': u'schmalliso', u'name': u'Allison Moore', u'email': u'allison.moore@10gen.com'}

Message: DOCS-4941: rephrases prereq for upgrading from pre-2.6

Signed-off-by: kay <kay.kim@10gen.com>
Branch: master
https://github.com/mongodb/docs/commit/e32d55ec2fea327dc6dbd31788affd75c70e9916

Generated at Thu Feb 08 07:49:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.