Difference between revisions of "Pmbootstrap release"

From postmarketOS
Jump to navigation Jump to search
(link to previous commits. they contain the MR ID now (thanks to mrhlpr), so no need to look at closed MRs separately)
(it's a good idea to increase the minimum apk version with every release)
Line 1: Line 1:
 
Checklist for creating a <code>pmbootstrap</code> release:
 
Checklist for creating a <code>pmbootstrap</code> release:
  
* set version in <code>pmb/config/__init__.py</code> to the new version
+
* <code>pmb/config/__init__.py</code>:
 +
** bump pmbootstrap version
 +
** update the apk version to the current one in Alpine Linux
 
* [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 06:57, 21 January 2019

Checklist for creating a pmbootstrap release:

  • pmb/config/__init__.py:
    • bump pmbootstrap version
    • update the apk version to the current one in Alpine Linux
  • 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