Uploaded image for project: 'PuppetDB'
  1. PuppetDB
  2. PDB-4475

Bump versions, push directly, and tag (PuppetDB 6.5.0)

    Details

    • Type: Task
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PDB 6.5.0
    • Component/s: None
    • Labels:
      None
    • QA Risk Assessment:
      Needs Assessment

      Description

      emphasized text(Initial planned release date: 2019-08-21)

      (if you're making the first release off a new branch you may already have done some of this)

      • Check that there aren't any essential updates to ezbake needed in this release before pushing a non-snapshot version and tagging.

      If this is a PE release, disable automatic promotions:

      • Go to the CI pipeline for the version being released and select the Conditional Promotion Trigger job. Click the disable button (the job's circle indicator should be gray now).

      Set the real version for release:

      • Remove the -SNASPHOT portion of the verison in project.clj in puppetdb and push directly to the branch you're releasing.
      • Go into the '#release-new-new' Slack channel to make yourself a tag

      ! tag puppetdb <version> at <sha> with <version>

      • Remove the -SNASPHOT portions of the versions in the file 'version' and project.clj in pe-puppetdb-extensions and push directly to the branch you're releasing.

      Be sure to set the same version to pe-pdb-verion and pdb-version directly

      • Go into the '#release-new-new' Slack channel to make yourself a tag

      ! tag pe-puppetdb-extensions <version> at <sha> with <version>

        Attachments

          Activity

            People

            • Assignee:
              rob.browning Rob Browning
              Reporter:
              nirupama Nirupama Mantha
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Due:
                Created:
                Updated:
                Resolved:

                Zendesk Support