On Sat, 18 Nov 2006, Les Mikesell wrote:
> > > What's the advantage of the tester pulling a branch revision
> > > number instead of a tag?
> >
> > As I said, your workflow is clearly different from mine. I'd expect
> > almost every revision in the stable branch to be a candidate for
> > testing, so there's no reason to tag them before testing.
>
> Is there a reason not to?
Tagging is extra effort, extra entries in the logs, extra directories
in the view presented by a repository browser. Why use tags (which are
really copies in subversion) if you can get away with revision numbers?
> > I am sorry that what was intended as a simple "if you are not
> > careful your tag will end up with mixed revisions and that can be
> > confusing" has turned into such a long thread.
>
> Sorry to drag it out then, but coming from CVS where tagging is the
> only way to represent a known state [...]
With CVS, I usually used "-r ${branch} -D ${date_time}" to represent
a candidate for testing. I am aware that that that checkouts with
the -D flag don't always do the right thing in CVS, especially in
conjunction with vendor branches, but they always worked well enough for
me. Revision numbers in subversion are a more reliable way of getting
the same effect.
--apb (Alan Barrett)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Nov 19 08:08:01 2006