refer to http://weblogs.asp.net/bsimser/archive/2008/05/06/day-to-day-with-subversion.aspx
this is most like our case, but still have problems about real
operation.
when we branch and add new feature v1.1 in branch,other functions like
progress to next feature.
in our case we has three team to develop project
designer (D),artist(A),programmer(P)
D response produce function spec documens first
A draw pics use D spec
P coding use D spec
so milestone v1.1 sequence would be
D first finish their job v1.1 ,then to v1.2
A second finish their job v1.1 then to v.1.2
P final finish their job v1.1 then to v1.2
if we branch v1.2 to add new feature,the code will still v1.0 status
that would be large code to merge back to trunk and v1.2 isn't it?
and if D works fast they could progress to v1.3 and P still in v1.1
coding
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2454521
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-03-03 17:55:13 CET