Optional tag after commit

Bug #273182 reported by Niklas Andersson on 2008-09-22
Affects Status Importance Assigned to Milestone
Bazaar Plugin for Eclipse

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:

Section 3.7.2 "Tagging a release" http://doc.bazaar-vcs.org/bzr.dev/en/user-guide/index.html

See also


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.

Guillermo Gonzalez (verterok) wrote :

Thanks for reporting this. (and the details of the requirement)


Changed in bzr-eclipse:
importance: Undecided → Medium
status: New → Confirmed

I'm working a Tag Action. As the bazaar documentation describes it. For starters it will be a separate action, we can later enhance it and maybe use of it in conjunction with other actions (i.e Commit).

Changed in bzr-eclipse:
assignee: nobody → craighewetson
description: updated

Don't have time to work on this in the short term.

Changed in bzr-eclipse:
assignee: Craig Hewetson (craighewetson) → nobody
xaav (xaav) on 2011-07-14
Changed in bzr-eclipse:
status: Confirmed → Triaged
Changed in bzr-eclipse:
importance: Medium → Wishlist
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions