Hello!
Consider this: when your project depends on the latest version of
Widget_1, your project is in a fragile state. As soon as someone
makes a bad commit to Widget_1, your project suddenly does not work
anymore. If I were you, I would want to avoid such tight coupling of
projects, therefore I'd always use an explicit revision in
svn:externals. I would only update the revision number when I'm sure
I need the new version of the Widget_1 (because it has useful new
features or fixed bugs). When such a version becomes available, I
would update the revision number in svn:externals, then run some
tests to make sure it does not require any updating of my project
(e.g. due to changes in interface), and only then I would commit the
change of the svn:externals property (along with compatibility
fixes, if any).
Therefore I'd always use explicit revisions for svn:externals.
If that approach does not suit you, you may want to, for example,
only use svn:externals without explicit revision for the trunk (to
keep up with the Widget_1 without additional hassle), but then you
should always remember to add explicit revision information when you
create tags/branches of your project. To accomplish this, you may
create tag/branch not from the Repo Browser, but from a WC, in which
you have added the explicit revisions for all svn:externals
properties just for the sake of tagging/branching. This approach can
be scripted/automated.
K> If there is some way of using Subversion differently to accomplish
K> the
K> goals that I've described above, feel free to let me know. As it is,
K> one needs to peruse the checkout log and manually determine which
K> things changed after the release...or simply Zip the sources up and
K> maintain that as another archive of what 'really' was there when the
K> repo was at the level used in the release.
People often start using version control tools exactly to get rid
of such zipped source archives.
---=====---
Alexander
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1233812
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-02-26 18:01:31 CET