'make release' does not release to Launchpad
Bug #623486 reported by
Jonathan Lange
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| testtools |
Fix Released
|
Wishlist
|
Jonathan Lange | ||
Bug Description
Releasing to Launchpad is just as important to me as releasing to PyPI. The 'make release' command should:
* Change the "next" milestone to match the version number (X.Y.Z)
* Create a new "next" milestone
* Make a release for X.Y.Z
* Upload the tarball & signing file for the release
* Change any associated bugs on X.Y.Z to be fix released.
Related branches
lp:~jml/testtools/automate-lp-release
- testtools developers: Pending requested
-
Diff: 303 lines (+239/-17)4 files modifiedMakefile (+2/-1)
NEWS (+3/-0)
_lp_release.py (+228/-0)
doc/hacking.rst (+6/-16)
| Changed in testtools: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Changed in testtools: | |
| importance: | Low → Wishlist |
| Changed in testtools: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Jonathan Lange (jml) |
| Changed in testtools: | |
| status: | In Progress → Fix Committed |
| milestone: | none → next |
| Changed in testtools: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
