Pmbootstrap release

From postmarketOS
Revision as of 10:05, 3 March 2019 by Ollieparanoid (talk | contribs) (apk_tools_static_min_version: clarify variable name)
Jump to navigation Jump to search

Checklist for creating a pmbootstrap release:

  • pmb/config/
    • bump pmbootstrap version
    • update apk_tools_static_min_version to the current one in Alpine Linux
    • commit with the message "Prepare x.x.x release"
  • tag a release in gitlab
    • fill out "release notes" (we can use markdown there), leave "message" empty
    • look at the previous commits and copy paste the commit message titles, including the MR ID, like done in the previous tags). Sort by features, fixes and other.
  • update the pypi release (see the script in #1679)
  • update the pmbootstrap aport in pmaports (change the pkgrel, update the checksum, build)
  • if future changes in pmaports will require the new pmbootstrap version, increase it in pmaports.git's pmaports.cfg file