Optional tag after commit
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar Plugin for Eclipse |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
In the commit dialog we should add a "tag after commit"-checkbutton + text-area where we set the version-tag. (I think using the same style as you've done with Author and Fixes).
Then we have the option to do a commit and in the same way tag the commited tree with our desired version.
If the issue should arise that we DO want to tag a modified tree, without those modifications we could add a separate "bzr tag" in the future.
See documentation:
http://
Section 3.7.2 "Tagging a release" http://
See also
http://
Scenario:
Niklas works on his project and want to create a release. 0.9.0. He uses the "tag-feature" to set the version and pushes the code to Launchpad.
Changed in bzr-eclipse: | |
status: | Confirmed → Triaged |
Changed in bzr-eclipse: | |
importance: | Medium → Wishlist |
Thanks for reporting this. (and the details of the requirement)
Regards