Re: Repository Layout - One Vs. Many

"Crucius, Wesley" <WCrucius@sandc.com> writes:

> I'm still struggling with this one myself. I understand your explaination
> and I can accept it completely. I just want a way to be able to go to the
> repository and get the svn revision that "is" release version XX.YYY of my
> application.

Dude, that's what tags are for. See http://svn.collab.net/repos/svn/
for examples.

> I don't want want to have to maintain a cross-reference list
> independently of svn, and tagging seems to be problemmatic for
> TortoiseSVN because it really slows down explorer with, for example,
> 6 projects and a total of around 200 tagged revisions.

Is that because you actually have all 200 of those tags on your local
disk? If so -- don't do that! :-)

> So I thought maybe a label property that manually gets set prior to
> commits of what would be release versions. The problem with this is
> that there does not appear to be a way to determine what is the
> revision number of a revision whoose label property has a value of
> XX.YYY. Please help me out if I'm missing something... Maybe I'm
> missing the most obvious solution here? Just put the release
> version string in the commit message????

You could do that if you had to. I mean, if revision 4589 was the
revision that solidified your product's version 2.01, you could retroactively
change 4589's log message to have some greppable string:

   RELEASE-TAG: ProductName Version MM.mm.pp

But seriously, it sounds like your real problem is that some element
of your workflow, combined with some performance issues with
TortoiseSVN and/or Subversion, is keeping you from doing The Right
Thing.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 25 17:21:35 2004