Multiple feature branches and continuous integration -


i've been doing reading continuous integration , there scenario occur don't understand how deal appropriately.

we have stable mainline/trunk branch , create branches features. each developer keep own feature branches date merging trunk branch on regular basis. entirely possible 2 or more feature branches created , worked on over period of several weeks or months. in time many releases of software deployed. confusion arises.

it changes 1 feature branch cause merge conflicts other feature branches. ci suggests should merge trunk @ least daily resolve conflicts quickly. however, may not want merge feature code trunk because may not finished or may not want feature available in next release. so, how deal scenario , still follow ci principles of daily code integration?

there no feature branches in proper ci. use feature toggles instead.


Comments

Popular posts from this blog

python - Scipy curvefit RuntimeError:Optimal parameters not found: Number of calls to function has reached maxfev = 1000 -

c# - How to add a new treeview at the selected node? -

java - netbeans "Please wait - classpath scanning in progress..." -