Uploaded image for project: 'OCMUI - OpenShift Cluster Manager UI'
  1. OCMUI - OpenShift Cluster Manager UI
  2. OCMUI-3034

use official releases & automatic changelog

    • 3
    • OCMUI Core Sprint 266

      in the uhc-portal github repo':

      • start tagging releases, and use github's 'releases' tags. as we don't use versioning ATM, tags may be named after the release's date (in unambiguous format)
      • use github's automatically generated release-notes feature to replace our current method
      • update the release PR template, to replace the link to release-notes
      • update the release-to-prod' wiki page, to include these in the official release process
      • deprecate the release-notes wiki page, by adding a notice with a link to the new page, at https://github.com/RedHatInsights/uhc-portal/releases
      • announce the 2 prev' items in slack

      notes

      • versioning is out of scope at this time, as it'd require fundamental change to the dev' workflow: if we do it, we'd wanna have semantic-versioning, which will necessitate new kind of awareness from developers IRT change types (e.g. fix = patch, feature = minor, breaking changes = major)
      • tags creation in GH UI is limited - tags can only be created for recent commits (24 hours?). for the release process, and to ensure consistency, it'd be best to do it from the command line

              emalka@redhat.com Lee M
              emalka@redhat.com Lee M
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: