-
Notifications
You must be signed in to change notification settings - Fork 38
Release process
(it is assumed that you've already cloned the cgimap repo)
- Create a new branch
git checkout -b patch/issue_1234
-
Do the necessary code changes
-
Build and run unit tests
make V=0 -j7
make check
-
Commit changes
-
Upload branch
git push origin patch/issue_1234
- Create a Pull request on GitHub, discuss changes
A repository owner or collaborator can then merge the pull request into the master branch, assuming unit tests pass.
Important
Outdated info! The release process has changed since release 2.0.0.
(Steps for repo owners or collaborators)
-
Check out master branch
-
git pull -
Edit configure.ac, change version number
-
Create new commit "Bump version to 0.x.x" (see git log)
-
Push to GitHub
git push origin master
-
Checkout ubuntu/bionic branch
-
Merge master branch
-
Add new version to debian/changlog
-
Commit change
-
Push ubuntu/bionic branch to gitub
(An Ubuntu Launchpad user is required at this point, sign up involves signing some Code of Conduct document, uploading pgp public keys, etc. Refer to the Ubuntu Launchpad website for details: https://launchpad.net)
- Create tar ball
tar --exclude='openstreetmap-cgimap/.git' --exclude='openstreetmap-cgimap/debian' -jcvf openstreetmap-cgimap_0.9.0.orig.tar.bz2 openstreetmap-cgimap
-
Go to openstreetmap-cgimap directory
-
Sign the new version with your pgp key (has to match the one on launchpad)
debuild -kPGP_KEY -S -sa
- Push to launchpad
dput ppa:mmd-osm/cgimap openstreetmap-cgimap_0.7.4-1~bionic1_source.changes
Once the build process has finished, the new PPA version can be copied over to https://launchpad.net/~osmadmins/+archive/ubuntu/ppa (needs to be triggered by osmadmins)
See https://launchpad.net/~mmd-osm/+archive/ubuntu/cgimap/+packages
- Tag the new version
Example:
(checkout master branch first)
git tag v0.7.4
- Upload tag to GitHub
git push origin v0.7.4
- Based on the new tag, create a new release on GitHub