branching and merging - svn vendor branch with out-of-order releases -
how deal svn vendor branches when releases 3rd party vendor come out-of-order in version number. eg, consider releases in order:
- 1.0.0
- 2.0.0 alpha
- 1.0.1 (minor point release)
- 2.0.1 beta
- 1.1.0 (new features added)
- 2.0.2 final
we merge trunk various versions of above, depending on stage project in.
what's best way handle in svn vendor branches? should each release committed \current? history preserved properly? also, depending on amount of changes, lot of space wasted going , forth between versions (we're talking large software packages).
it's important me keep merge history, i'd keep using \current recommended svn red book. differences between versions might dramatic wouldn't make sense keep every version on same development line.
Comments
Post a Comment