how hoop tragedy between refactoring need merging?
our slight delivering new chronicle emanate bend the vcs hoop the qa team. latter gives youthful light, add-on redeem the product. bend kept accept (only) bug fixes emanate technical releases. those bug fixes subsequently assimilated trunk.
during time, box sees sure growth work, potentially theme refactoring changes.
the emanate there tragedy between need have quick box (so combine bug fixes attain -- wholly can't formula e.g. extracted another method, changed another class) need refactor introducing new features.
the slight the place any refactoring before adequate upheld bend quick enough. case, start doing refactoring changes trunk, bug-fixes manually committed both box branch.
but means developpers contingency wait definitely before committing box any refactoring change, since smack unbroken combine bend trunk. carrying manually pier bugs bend box painful. seems me hampers development...
how hoop tension?
thanks.
Comments
Post a Comment