Difference between revisions of "Pmbootstrap release"

From postmarketOS
Jump to navigation Jump to search
(add category:guide)
(apk_tools_static_min_version: clarify variable name)
Line 3: Line 3:
 
* <code>pmb/config/__init__.py</code>:
 
* <code>pmb/config/__init__.py</code>:
 
** bump pmbootstrap version
 
** bump pmbootstrap version
** update the apk version to the [https://pkgs.alpinelinux.org/packages?name=apk-tools&branch=edge current one in Alpine Linux]
+
** update <code>apk_tools_static_min_version</code> to the [https://pkgs.alpinelinux.org/packages?name=apk-tools&branch=edge current one in Alpine Linux]
 
** commit with the message "Prepare x.x.x release"
 
** commit with the message "Prepare x.x.x release"
 
* [https://gitlab.com/postmarketOS/pmbootstrap/tags/new tag a release in gitlab]
 
* [https://gitlab.com/postmarketOS/pmbootstrap/tags/new tag a release in gitlab]

Revision as of 10:05, 3 March 2019

Checklist for creating a pmbootstrap release:

  • pmb/config/__init__.py:
    • 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