Fair point Roman, the potential community/communities of developers is
one of the parameter.
Having a quick look at the different components dependencies, I don't
see any links between them although I would have expected some of them
to use sli4j for their own logging, JUnice for their unit tests...
I we want to keep frontier between these components (as well on a
community as on a code dependency), then one big git repo doesn't make
sense. I am more interested in a unique platform based approach
(although keeping the modularity).
Thx, Eric
On 07/11/2012 16:31, Roman Shaposhnik wrote:
On Tue, Nov 6, 2012 at 1:48 PM, Eric Charles <e...@apache.org> wrote:
Yes, the 11 components are unrelated, but I just find the release process
such a pain that I fear to go to independent lifecycle.
I think the real question is whether you'd expect different sub-communities
of developers tending to them, or whether you'd expect a singe community
where folks work on all/most of them.
In my experience, the mechanical policies of releases/SCM should follow
from how the community is expected to operate, not the other way around.
Just my 2c.
Thanks,
Roman.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
