← Back to team overview

openerp-community team mailing list archive

Re: bzr workflow suggestion: DaggyFeatures

 

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 conflicts, and I have to make several branches. So I don't believe this can work for new features because they often rely on refactoring/improvements made in the trunk. When they don't, it's a pitty because a lot of refactoring is still needed everywhere To make it work would take each developer start from a stable tag and merge in all the branches that contain related improvements. Considering that this is useful less than 6 month (ETA of new stable), backporting new modules seems easier than all this bookkeeping.

Lionel.



References