[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Rapidly-changing revision number

From: Talden <talden_at_gmail.com>
Date: 2006-10-14 02:30:35 CEST

Frank Gruman
> > My preference and the way I have my repos set up - each project has it's
> > own repository. If I want to do some sort of work/testing/anything to
> > one, I don't have to kill the whole development process to do it. From
> > the developer perspective, they know that their code is segregated by
> > project. They don't know or care that there are one or many repositories.

Kenneth Porter
> Setting up projects in their own repositories makes sense if they're
> independent. If one project depends on another, or they share a common
> library project, then a shared repository insures that changes in the
> depended-upon project that break the dependent project can be identified
> and rolled back.

I guess here's where the 'term' project breaks down.

If you have two products (that is, artifacts that are delivered on
different schedules whether they are bundled together or not) then
they should have separate repositories.

If two of these 'products' have a shared library (a sub-product) then
it too should have it's own repository, and it's own release process.
Why have Product A dependant on the progress of Product B just because
they share a library - have releases of the library and treat it as a
product from its team. Product A shouldn't have to be developed
against the moving target of its dependancy due to the outside
influence of Product B.

That said, the NEED to place them in separate repositories is
absolutely only important to you if the repository revision number has
some relevence to your development process other than the
identification of the repository at a point in time (and the effect of
a commit rN-1:rN).

I would absolutely recommend separate repositories if there really are
multiple teams working on these projects and subprojects all at once
(just due to the commit activity levels)...

> Alas, the real world is full of coupling between projects, so one is
> tempted to put all projects in one repo. But separate repos tend to be
> easier to admin. So it depends on just how much coupling there is between
> the projects.
> If you've got good interface boundaries that can be represented by a repo
> tag, then separate repos are tenable, as changes to the library are
> captured in tags and the dependent project can specify the tag(s) that it's
> compatible with.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Oct 14 02:31:16 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.