[asterisk-scf-dev] Consolidate git repos?

[Kevin P. Fleming]

On 10/13/2010 08:16 AM, Simon Perreault wrote:

> What is the perceived advantage of fine-grained repositories?

It doesn't force a collection of (potentially dozens of) components to
be released in lock-step. It doesn't create tags on components (to bump
the version number) that are being released only because some other
component had a serious bug that caused an out-of-schedule release to be
made.

Keep in mind that one noticeable difference between KDE and Asterisk SCF
is that the published interfaces that components implement and consume
are not defined in the component itself; there is a single repository
that holds all the published interfaces (at least the ones that aren't
primarily private to a single component). It's not possible to produce a
new version of a component that doesn't implement or consume its
published interfaces in the same way as it did before without a new
version of the 'core interface' repository; otherwise, the component
would just be 'broken'.

It's still early enough in the process that none of this is carved in
stone/concrete/titanium/trilithium, and this would probably be a
worthwhile topic to talk about at the devcon after Astricon in a couple
of weeks.

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
skype: kpfleming | jabber: kfleming at digium.com
Check us out at www.digium.com & www.asterisk.org