You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@subversion.apache.org by Jie <yw...@163.com> on 2016/12/29 15:17:24 UTC

Please give me some advice, about using Cherrypicking for project management

Hi,


There are four branches in my project: dev, sit, uat and production.
I am planing to apply Unified Change Management idea to project management (like CCCQ)


 Here is my plan:
Record commit info to TaskID’s description. For example, 


TASK-001:  
bundles revision: 100 and 110


TASK-013:
bundles revision: 105




When TASK-001 and TASK-013 are ready to deploy to sit, I will merge all the revisions in TASK-001 and TASK-013 to branches/sit.
In the working copy(always updated and clean) of sit branch, use command by turn: 
svn merge -c 100 ^/project/branches/dev
svn merge -c 105 ^/project/branches/dev
svn merge -c 110 ^/project/branches/dev


And when the TASK-001,013 are ready to deploy to UAT, I will merge the revisions to UAT branch (from branch dev).


Is it possible to do this?  Is there any potential risk for this process?  
Please kindly give me some advice. Thank you!


If anybody has such experience, please share with me.  Thanks!