Sorry, responded directly to Gary instead of the list...
-----Original Message-----
From: Henderson, Michael D
Thanks. Right now I'm exploring how we're going manage the process in
SVN. If you think this approach will cause extra work, do you have a
suggestion on less VSSy and more SVNy solution?
Mike
-----Original Message-----
From: Gary Feldman [mailto:g1list_1a@marsdome.com]
Henderson, Michael D wrote:
...
> The obvious solution would be for me to physically create the
"releaseNumber"
> directory under branches/ and check it in. Then I should be able to do
the copy,
> right? Is there a better way to do this? The rational for creating
ticketNumber
> under releaseNumber is to track which tickets are in each release.
Then we could
> run svn log and filter on that releaseNumber to zero in on the changes
when
> we're ready to merge back to the trunk.
The svn mkdir command takes a URL, so you can create the releaseNumber
directory in the repository directly, not that creating it locally and
checking it in is that much work.
Note that you'll need to do a bit of scripting work to filter the svn
log. Furthermore, you may be setting yourselves up for multiple merges
if each ticket is getting its own branch. I'm not sure that you aren't
better off keeping this information in your ticket tracking system
instead, or even writing a checkin script that does the correlation.
Gary
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 25 17:18:32 2004