[DOCS-8896] Simplify repo.mongodb.(com|org) repository layout. Created: 28/Sep/16 Updated: 30/Oct/23 Resolved: 21/Jan/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Emily Hall | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 6 years, 3 weeks, 4 days ago | ||||||||
| Description |
|
Currently, we publish packages for our releases with the following layout:
The stable/unstable repositories have the property that, when "current" stable/unstable changes to different release series, after a stable release, the upgrade mechanism on a user's system will automatically upgrade between versions automatically which is often not operationally desirable. We only document the repository for the stable release series, though we have erroneously documented the stable repositories in the past. This ticket covers a number of changes, so that for repo.mongodb.org and repo.mongodb.com we will:
While users will generally not have the unstable repo configured, as it was never documented, some users may have the stable repository configured. If you have stable or unstable repositories configured, your package manager will report an error when you attempt to update these packages. If you encounter this, please change your configuration to match the repository for your current branch: at the time of writing, the current stable branch is 3.2 and the current unstable branch is 3.3. Sorry for any confusion. |
| Comments |
| Comment by Kay Kim (Inactive) [ 21/Jan/18 ] |
|
Overly aggressive ticket creation by the ticket maker script. |