Yep, I mostly branch my bug-fixes from a stable "x.y.0" tag, which has 2
more advantages :
* it makes uploading the branch to LP much faster
* it often allows the same branch to be merged in several stable
versions AND in trunk.
However there are cases where this is not possible because of con
I'd like to propose a workflow enhancement related to bzr branching and
new feature development. A problem with the way bzr stores history makes
it difficult to cherry-pick changes [1]. This is really a problem when
backporting bugfixes or new features.
A sited solution in the bug case is Dagg
2 matches
Mail list logo
