Details

    • Sub-task
    • Status: Resolved
    • Normal
    • Resolution: Done
    • None
    • None
    • None
    • None
    • Agent
    • Agent 2017-06-28, Agent 2017-07-12
    • No Action

    Description

      (Initial planned release date: 2017-06-27)

      Create the release branch for the release and switch PE promotions from stable to the release branch.

      NOTE When creating the release branch, verify that components that will not be updating for this release are still pinned to tags:

      • run rake package:implode package:bootstrap vanagon:check_tags
      • Verify any components that are not updating are still pinned to tags using the output from above
      • If there are incosistencies, open a PR to re-pin each non-updating component to the last tag
      • Create a branch called 5.0.0-release in the puppet-agent project
      • Update ci-job-configs with the following changes:

      ~ there is an entry with the following:

                - 'puppet-agent-suite-pipeline-daily':
                  <<: *stable_suite_targets
                  scm_branch: '1.9.2-release'
          

      Update promote_into: and pe_promotion: to the appropriate values, which should be considered based on the needs of the release

      Update set_disabled: to False

      ~ Update all entries listed as 'puppet-agent-suite-pipeline-hardware' with the following:

      There is an entry listed with scm_branch: '#.#.#-release', update it to '5.0.0-release'

      Update the '5.0.0-release' entry with

              set_disabled: to False
              

      https://confluence.puppetlabs.com/display/RE/Puppet+Agent+Release+Branching

      Attachments

        Activity

          People

            maggie Maggie Dreyer
            geoff.nichols Geoff Nichols
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Zendesk Support