svn - Subversion branches and release plan -

svn - Subversion branches and release plan -

currently next simple release plan our projects follows;

developers committed changes subversion repository. build changes qa server. build changes production server.

the issue utilize 1 single source code set in svn trunk these steps.

therefore cannot command qa server release (ex: avoid requirements).

we have complicate release occurrence days have release 5-6 times qa server.

i guess using subversion branches can overcome issue. can create separate branch qa/live server release , can merge necessary changes head/trunk.

or other way around? maintain head/ trunk version qa/ live server release , create branch development commits.

what right way?

please allow me know whether there improve way/tool handle situation.

thanks.

there quite popular approach branches in svn. it's described here: http://svnbook.red-bean.com/en/1.7/svn.branchmerge.commonpatterns.html

in project (one-person project separate release cycle) utilize both release , feature branches , have no problems.

exact branch policies may vary, here works me:

trunk (only one): automatic tests pass, contains completed features , bug fixes feature branch (usually multiple): dedicated single feature or bug fix, builds, automatic tests pass, after completion reintegrated trunk , deleted stabilization branch (may multiple, one): dedicated planned release, automatic tests pass, used generate builds sent qa, internal/external release tags created it, fixes or features may merged here trunk

svn release-management subversive