[DOCS-104] Move the "Upgrade Version" section out to own page and include more upgrade scenarios (e.g., 1.6 --> 2.0) Created: 10/Jan/12 Updated: 30/Oct/23 Resolved: 19/Mar/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | v1.1 |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Daniel Pasette (Inactive) | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 10 years, 48 weeks, 1 day ago | ||||||||
| Description |
|
http://www.mongodb.org/display/DOCS/2.0+Release+Notes#2.0ReleaseNotes-Upgrading This is mixed in with too much other extraneous and confusing information. We should have a single page which links to all upgrade paths and considerations. |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 19/Mar/13 ] |
|
closing this ticket, because the work is mostly acomplished, and I think that the duplicate ticket has a more clear and useful scope/goal. |
| Comment by Sam Kleinman (Inactive) [ 24/Feb/13 ] |
|
dan@10gen.com 2.4 has/will have this kind of organization. Do you want us to apply this change to the 2.2 release-notes/upgrade information? Otherwise will close this ticket... |
| Comment by Bob Grabar [ 07/Jan/13 ] |
|
This is still a good idea. We should do it for 2.4. |
| Comment by Sam Kleinman (Inactive) [ 11/Jul/12 ] |
|
we can certainly do this with minimal overhead for 2.2 but I'm not sure that this actually makes sense. Current thoughts? |