Difference between revisions of "Pmbootstrap release"

From postmarketOS
Jump to navigation Jump to search
(link to apk-tools in Alpine's package search)
Line 4: Line 4:
 
** 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 the apk version 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"
 
* [https://gitlab.com/postmarketOS/pmbootstrap/tags/new tag a release in gitlab]
 
* [https://gitlab.com/postmarketOS/pmbootstrap/tags/new tag a release in gitlab]
 
** fill out "release notes" (we can use markdown there), leave "message" empty
 
** fill out "release notes" (we can use markdown there), leave "message" empty

Revision as of 09:40, 3 March 2019

Checklist for creating a pmbootstrap release:

  • pmb/config/__init__.py:
  • tag a release in gitlab
    • fill out "release notes" (we can use markdown there), leave "message" empty
    • look at the previous commits to write a good description of what changed
  • 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