Release command's description is circular
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ezbzr |
Fix Released
|
Low
|
Tim Powell | ||
Bug Description
The short description is currently:
'Releases' the current branch to a target branch.
Nathaniel's original description on the Bazaar website was:
Merges a local branch into a remote one
I think Nathaniel's description better depicts the intended usage and is more informative. We may also want to look at the long description and clean it up. The idea is that Release is functionally equivalent to having a current (local) branch, going to a target branch (generally on a remote server) and merging in the original local branch. This lets you work from just one server instead of two and to do merges and not just pushes. Instead of being limited to "merge other into this" you effectively have "merge this with other"
It may also be worth noting, if it isn't already, that release does not update the working tree of the target branch if it is remote. In our usage this doesn't matter because we do this through cron running foreach.
| Tim Powell (theuiguy) wrote | #1 |
| Changed in ezbzr: | |
| status: | New → Fix Committed |
| importance: | Undecided → Low |
| assignee: | nobody → Tim Powell (theuiguy) |
| status: | Fix Committed → Fix Released |
I'm going to call this fixed as of version 0.2.7. The description is now "Merges the current branch into a target branch." and the long description has been reworked as well.