[DOCS-5908] Should we document upgrading to minor revisions using package managers? Created: 27/Jul/15  Updated: 30/Oct/23  Resolved: 01/Nov/22

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

Type: Improvement Priority: Major - P3
Reporter: Ramon Fernandez Marina Assignee: Andrew Aldridge
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by DOCS-8072 Comment on: "manual/tutorial/install-... Closed
Participants:
Days since reply: 1 year, 14 weeks, 1 day ago
Epic Link: DOCSP-1769
Story Points: 0.5

 Description   

We document how to install MongoDB using different package managers and how to manually upgrade to the latest minor revision, but I don't think we have any documentation on how to upgrade a MongoDB installation to the latest minor revision (e.g.: from 3.0.1 to 3.0.4) using package managers.

A user in SERVER-19586 was concerned about his configuration files being preserved. I know that Debian/Ubuntu do the right thing and either preserve the old config file or ask the user what to do. Yum seems to do the same, but the documentation (here and here) doesn't answer all questions IMO.

Should we add a section on our docs on how to upgrade to the latest minor revision using package managers?



 Comments   
Comment by Education Bot [ 01/Nov/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Comment by Ernie Hershey [ 28/Jul/15 ]

I agree with the upshot -

  1. Add an "upgrade" section in each package manager instructions page
  2. Add a note about using the package manager instructions in the "replace binaries" section of the upgrade-revision page
Generated at Thu Feb 08 07:51:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.