-
Type:
Bug
-
Resolution: Done
-
Priority:
Blocker - P1
-
Affects Version/s: None
-
Component/s: manual
-
Labels:
-
Environment:
*Location*: http://docs.mongodb.org/master/release-notes/3.0-upgrade/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.94 Safari/537.36
*Referrer*: http://docs.mongodb.org/master/release-notes/3.0/
*Screen Resolution*: 1920 x 1080
*repo*: docs
*source*: release-notes/3.0-upgrade
*Location*: http://docs.mongodb.org/master/release-notes/3.0-upgrade/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.94 Safari/537.36 *Referrer*: http://docs.mongodb.org/master/release-notes/3.0/ *Screen Resolution*: 1920 x 1080 *repo*: docs *source*: release-notes/3.0-upgrade
On this page - "manual/release-notes/3.0-upgrade.txt"
I think all we need to say is that people need to install the new repo files - basically following the installation instructions as if they don't already have packages installed. The old repos shouldn't conflict with new ones and with both old/new installed, the newer packages in the new repos should just upgrade over the old ones as if they were from the same repo.
- is related to
-
-
- Closed
-
-
SERVER-16744 Targeted community build packages and repo
-
- Closed
-
-
DOCS-4621 Update install docs with new targeted community build package information
-
- Closed
-