Steve Folly wrote:
> Hi,
>
> I'm having difficulty trying to map our CVS usage onto Subversion. Let
> me explain.
>
> There are (currently) only 4 software developers working and
> committing in the main trunk of our repository, on 1 (perhaps 2)
> projects at a time.
>
> For a release, somebody will be assigned the job of creating a
> working copy of the main trunk and updating files as required to
> create a stable build. Meanwhile commits are still happening in the
> main trunk, but the release coordinator is only updating certain files
> required for the build. (99.9% of the time it's all files being
> committed, but some changes wont be required). The advantage of doing
> it this way rather than creating a release branch is that we don't
> need to merge changes from main trunk to branch; just update as and
> when. At a stable point (usually 1 hour before delivery :), that
> working copy is tagged as the release.
>
> This is what I can't get my head around with subversion - how to pick
> and choose which commits go into a working copy? Consider three
> commits to the repository, A, B and C, performed over time in that
> order. How can I have a working copy with only commits A and C, but
> not B?
>
'svn switch' allows parts of the working copy to be switched to specific
revisions.
Ramaswamy
> Should we now be thinking about creating a branch for a release in
> subversion, then we can pick and choose which updates we want. The
> only disadvantage to this is (I think) that we have to manually (i.e.
> tell svn) to merge files from the main trunk to the release branch.
>
> Thanks for any helpful suggestions.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 9 15:09:45 2004