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)
Line 4: Line 4:
 
* [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
** look at the previous commits and merged MRs to write a good description of what changed
+
** look at the [https://gitlab.com/postmarketOS/pmbootstrap/commits/master previous commits] to write a good description of what changed
 
* update the pypi release (see the script in {{issue|1679}})
 
* update the pypi release (see the script in {{issue|1679}})
 
* update the pmbootstrap aport in pmaports (change the pkgrel, update the checksum, build)
 
* 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
 
* if future changes in pmaports will require the new pmbootstrap version, increase it in pmaports.git's pmaports.cfg file

Revision as of 21:23, 26 December 2018

Checklist for creating a pmbootstrap release:

  • set version in pmb/config/__init__.py to the new version
  • 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