[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Jie <ywhdjlc_at_163.com>
Date: Thu, 29 Dec 2016 23:17:24 +0800 (CST)

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!
Received on 2016-12-29 16:17:56 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.