2016-11-03 03:03:51 +00:00
|
|
|
Here are the steps to follow to create a new terminator release:
|
|
|
|
|
|
|
|
|
|
1. Ensure there are no local, uncommitted/unpushed modifications.
|
|
|
|
|
|
|
|
|
|
$ bzr status
|
|
|
|
|
|
|
|
|
|
2. Verify the code passes checks and tests
|
|
|
|
|
|
|
|
|
|
$ python setup.py test
|
|
|
|
|
$ python setup.py check
|
|
|
|
|
|
|
|
|
|
3. Update version number. Edit terminatorlib/version.py and set the
|
2016-11-23 04:54:16 +00:00
|
|
|
version number. Also edit terminator.spec and set it there. Edit
|
2017-02-26 17:37:22 +00:00
|
|
|
the debian/changelog to add new version. Update the Changelog
|
|
|
|
|
file if not already up-to-date.
|
2016-11-03 03:03:51 +00:00
|
|
|
|
|
|
|
|
4. Create the source distribution package
|
|
|
|
|
|
|
|
|
|
$ python setup.py sdist
|
|
|
|
|
|
|
|
|
|
5. Sign the tarball
|
|
|
|
|
|
|
|
|
|
$ gpg -u bryce@bryceharrington.org --armor --output
|
|
|
|
|
terminator-0.98.tar.gz.asc --detach-sig terminator-0.98.tar.gz
|
|
|
|
|
|
|
|
|
|
6. Upload to Launchpad
|
|
|
|
|
|
|
|
|
|
+ Create the appropriate Milestone
|
|
|
|
|
+ Create a matching Release
|
|
|
|
|
+ Upload the tarball and gpg signature to the Release
|
|
|
|
|
|
|
|
|
|
7. Tag the release in trunk
|
|
|
|
|
|
|
|
|
|
$ bzr tag 0.98
|
|
|
|
|
$ bzr push
|
|
|
|
|
|
|
|
|
|
8. Post announcements
|
|
|
|
|
|
|
|
|
|
+ Write a blog post
|
|
|
|
|
+ Create an Announcement on the Launchpad page.
|
|
|
|
|
Include a link to the blog post URL
|
