Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-25908

Simplify repo.mongodb.(com|org) repository layout.



    • Minor Change
    • Build 2016-09-19


      Currently, we publish packages for our releases with the following layout:

      • there is a repository for each release series (e.g. 3.0, 3.1, 3.2, 3.3) for stable and unstable releases.
      • we build a second copy of the current stable series into a stable repository.
      • we build a second copy of the current unstable series into a unstable repository.
      • we put all release candidates and nightlies into a testing repository.

      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:

      • have a repository for each release series (e.g. 3.0, 3.1, 3.2, 3.3) for stable and unstable releases. (no change)
      • publish all release candidates into the testing repository. (no change)
      • publish all nightlies into a new "development" repository (change, but not documented.)
      • remove the current stable/unstable repositories. (change).

      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.




            sam.kleinman Sam Kleinman (Inactive)
            sam.kleinman Sam Kleinman (Inactive)
            0 Vote for this issue
            6 Start watching this issue