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

new version package release process should be reviewed

    • Build

      major version upgrades that might break production servers as is in this case of 2.0.0 should be done manually

      i see that mongo-* 1.8.3 rpm were renamed to mongo18-* and 2.0 was introduced as mongo-* which resulted in auto upgrade to new version on my servers.

      i would advise to release new version as mongo20-, mongo22- and keep old as mongo18-*, no renaming.

            Assignee:
            backlog-server-build Backlog - Build Team (Inactive)
            Reporter:
            ootada ttt
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: