openhpc/ohpc

3.0 Checklist

koomie opened this issue · 1 comments

koomie commented
  • spell check documentation
  • verify correct version in docs
    • git sha
    • ohpc version in header
  • verify rpm version of docs-ohpc
  • verify url of ohpc-release package in ohpc-docs
    • el/x86
    • leap/x86
    • el/aarch
    • leap/aarch
    • openeuler/x86
    • openeuler/aaarch
  • double check rpm release strings have correct ohpc version (a project config setting in obs)
  • clean up page breaks in ohpc-docs
  • run Rel. Support -> Scan Package Release Numbers job and verify no issues detected
  • run Rel. Support -> Generate Package Counts and update relevant 3.x version page on wiki
  • update pointer to latest component list page in wiki sidebar
  • final reposync from Factory: Rel. Support -> Pull Repo
  • final manifest generation
  • update wiki component list -> output from Rel. Support -> Generate Component List job
  • update badge counters
  • disabled future builds in Factory (now using lock)
  • remove draft watermark
  • release tagging
    • tag ohpc repo
    • tag CI repo
    • tag wiki repo
  • finalize changelog
  • add changelog to release
  • build final dist tarballs
    • run build job in jenkins
    • update links & md5sums on release wiki page
  • complete jenkins run with dist tarballs
  • update links to ohpc-release RPMs on release page (N/A for micro release)
  • upload install guides to release page
  • update ohpc-release file download commentary on ohpc website (generally N/A for minor release)
  • make 3.x default branch on github
  • post to ohpc-announce
  • move final packages from .staging to final production location
  • alter [update] repo link to point to latest update revision in /repos/
  • update obs trigger to point to newer OBS factory version (3.1) ( now in trigger/python-github-webhooks/hooks/all)
  • update roadmap table in wiki
  • update table in wikipedia.org
  • backup infrastructure (obs/repos)
  • run job with release repo after update

A friendly reminder that this issue had no activity for 30 days.