[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/ |
||
| 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: It should say something like: |
| 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: Signed-off-by: kay <kay.kim@10gen.com> |