[DOCS-3546] Upgrade MongoDB to 2.6 docs don't mention packaged installs Created: 05/Jun/14 Updated: 21/Jul/14 Resolved: 21/Jul/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.8 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Stennie Steneker (Inactive) | Assignee: | Tim Slavin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 9 years, 30 weeks, 2 days ago | ||||||||
| Description |
|
The Upgrade MongoDB to 2.6 instructions refer to a binary-compatible “drop-in” upgrade and do not mention how to upgrade in packaged environments (eg. if you follow instructions to install on Ubuntu or RHEL. For an inexperienced user, the instructions on the upgrade page imply that downloading and copying over the binaries is the recommended path. I think there should be strong encouragement to use the packaged versions, where possible, and directions on how to upgrade from previous releases using package management. |
| Comments |
| Comment by Githook User [ 21/Jul/14 ] |
|
Author: {u'username': u'TimSlavinMongoDB', u'name': u'Tim Slavin (MongoDB)', u'email': u'tim.slavin@10gen.com'}Message: Signed-off-by: kay <kay.kim@10gen.com> |