svn - Using version control to keep multiple code branches up to date -
svn - Using version control to keep multiple code branches up to date -
i'm hoping able help me improve understand version command in scenario. we're thinking of either implementing visualsvn or mercurial, want our strategy figured-out first.
i'm part of 2 man development team working on porting , maintaining bespoke cms system. we're looking maintain "stable" branch, , each have our own dev branches required.
where we're not sure each client requires own customisations (templates, stylesheets, etc). i'd expect these branches stable. ideally we'd way ensure changes made stable (such merging dev branch in or adding hot-fix) pushed out client branches.
is there way ensure these client branches automatically brought forwards recent changeset ?
can take exclude files (such *.css) getting pushed client branches after initial branch operation ?
looking @ you'd able go each client branch , pull stable, merging latest changes in. in event end lots of client branches, there improve way ?
i've found questions seem offer advice
using version command non-hierarchical code?
practical way commit changes in source command multiple branches
version command multiple instances of developing code
how maintain branches date 'default' branch under mercurial?
apologies if i'm coming @ backwards, suggestions appreciated.
is there way ensure these client branches automatically brought forwards recent changeset ?
you going branch, pulling stable , merging.
can take exclude files (such *.css) getting pushed client branches after initial branch operation ?no, don't exclude files when merge. should instead construction files have base of operations file — phone call base.css
— , have client.css
additional style sheet. way can override things base.css
in client.css
needed and latest version of base.css
when merge stable branch.
you can utilize same scheme other files need alter on per-client basis: configuration files , themes.
looking @ you'd able go each client branch , pull stable, merging latest changes in. in event end lots of client branches, there improve way ?
nope, that's way works. can of course of study script create more convenient , cut down risk of errors.
svn version-control mercurial branch dvcs
Comments
Post a Comment