Document release process
This commit is contained in:
parent
f5f3a52d5d
commit
06bd199ff5
|
@ -0,0 +1,34 @@
|
|||
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
|
||||
version number. Also edit terminator.spec and set it there.
|
||||
|
||||
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
|
||||
|
||||
8. Post announcements
|
||||
|
||||
+ Write a blog post
|
||||
+ Create an Announcement on the Launchpad page.
|
||||
Include a link to the blog post URL
|
Loading…
Reference in New Issue