[DOCS-9972] Consistently label MONGODB-CR as deprecated Created: 06/Mar/17 Updated: 30/Oct/23 Resolved: 24/Mar/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Jackson | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 45 weeks, 5 days ago |
| Description |
|
This blog post, written when 3.0 was released, states that MONGODB-CR is deprecated. The HTTP interface requires MONGODB-CR to function and was deprecated in 3.2. We should mark MONGODB-CR as deprecated in all places where it is relevant. Going forward, we wish to minimize the number of "upgrade commands" which must be ran to upgrade a cluster from one version to another. This will simplify the upgrade process, and ensure that the system operates at a single consistent version. This implies that a future unified upgrade command will upgrade the authSchemaVersion to the latest value, which does not support MONGODB-CR. |
| Comments |
| Comment by Sarah Olson [ 24/Mar/23 ] |
|
Closing this out on the grounds that:
Based on this, closing as WON'T DO. Please don't hesitate to give me a shout or to reopen if you disagree. |