[DOCS-11888] Create documentation on upgrading from community to enterprise Created: 19/Jul/18  Updated: 30/Oct/23  Resolved: 09/Aug/18

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

Type: Task Priority: Major - P3
Reporter: Melissa Plunkett Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
backported by DOCS-1564 Document the upgrade path from Commun... Closed
backported by DOCS-2305 Add documentation for upgrading from ... Closed
Duplicate
duplicates DOCS-1564 Document the upgrade path from Commun... Closed
duplicates DOCS-2305 Add documentation for upgrading from ... Closed
duplicates DOCS-11082 Document how to convert an existing C... Closed
Participants:
Days since reply: 5 years, 26 weeks, 6 days ago
Epic Link: DOCSP-1769

 Description   

----------------------------

Original Description

This has been requested multiple times and still seems unsolved (see linked tickets). There is no clear documentation on upgrading from community to enterprise. Recently a customer asked how and to ensure I gave correct guidance I tracked down an authoritative answer from an internal resource. It would help our customers to document to upgrade process in the release notes, calling out any potential issues and linking to documentation explaining how to enable enterprise only features.
----------------------------

Description

Scope of changes (files that need work and how much)

Impact to other docs outside of this product

MVP (work and date?)

Resources (e.g. Scope Docs, Invision)



 Comments   
Comment by Githook User [ 09/Aug/18 ]

Author:

{'name': 'ravind', 'email': 'ravind.kumar@10gen.com', 'username': 'rkumar-mongo'}

Message: Fixing broken link for suse tarballs (DOCS-11888)
Branch: v4.0
https://github.com/10gen/mms-docs/commit/3de840985acd9d40590b81ea5d5125f496bd3fe1

Comment by Githook User [ 09/Aug/18 ]

Author:

{'name': 'ravind', 'email': 'ravind.kumar@10gen.com', 'username': 'rkumar-mongo'}

Message: Fixing broken link for suse tarballs (DOCS-11888)
Branch: master
https://github.com/10gen/mms-docs/commit/240a133ba1d39dd80595ff28f56c24a9233f3341

Comment by Githook User [ 08/Aug/18 ]

Author:

{'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-11888: single source upgrade to enterprise content
Branch: master
https://github.com/mongodb/docs/commit/567f209dc99a49729d9c9addf6a220576f48ad4c

Comment by Githook User [ 08/Aug/18 ]

Author:

{'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-11888: upgrade to enterprise
Branch: master
https://github.com/mongodb/docs/commit/f7cc9d5e89e75f3ba2749557c5b897801c13c147

Comment by Jonathan DeStefano [ 20/Jul/18 ]

I believe this effort was started at some point in time, but not sure what happened. Refer to DOCS-11082.

nick.larew When you are back from vacation can you provide some detail on this or recommend if we should start fresh?

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