RE: development of externals?

On Monday, November 26, 2007 10:45 AM -0500 "Bicking, David (HHoldings,
IT)" <David.Bicking@thehartford.com> wrote:

> I strongly encourage you to consider a binary compatability model for
> shared code. Manage changes to the code like an independant project and
> release binaries to the projects that use them. Those projects can
> choose to use the newer version, and fall back if there are problems. Of
> course, it all depends on how much disruption your teams want to accept.

Or specify a repository revision, or use a tag, when referring to an
external. If someone commits a change to the external reference, the
explicit revision in the reference will "prevent the bookmark from moving".
The effect is that the external references a known version, not the
unstable HEAD.

This allows each client project to control which version of the shared code
it will use, and to upgrade only when it's safe to do so.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 26 19:37:51 2007