I did some archeology. I brought up the issue back in June 2011, before
we had a mailing list (and when we still considered migrating to Eclipse
We have a number of loosely coupled projects. My suggestion would be
to manage them all in one single Eclipse Labs project, but with a
separate mercurial repositories for each project. Does this approach
... but there was little response, no objection either. Wayne was part
of that discussion. The fact that he didn't object reflects what he
said in . Other projects picked a similar approach, e.g. Hudson.
The motivation was the relative independence of the five projects.
Also, two projects will probably not see that much activity (rif11 and
I find the current configuration useful and the overhead minor.
Checking out a few repositories has to be done only once, and the
tagging for the release process should eventually be done with scripts
But I am also in favor of simplicity. So if there is a real *strong*
desire to merge the repositories, I'll be fine with that. So... how
strong is that desire?
I suggest to have separate repositories for product code, incubation
This is certainly something to consider once we leave incubation. For
now, I don't think this is necessary.
Michael Jastram (http://www.jastram.de
, +49 (162) 274 83 94)
Geschäftsführer, Formal Mind GmbH (http://formalmind.com
Wissenschaftler, Heinrich Heine Universität Düsseldorf (http://www.stups.uni-duesseldorf.de
1. Vorsitzender, rheinjug e.V. (http://www.rheinjug.de
rmf-dev mailing listrmf-dev@xxxxxxxxxxxhttp://dev.eclipse.org/mailman/listinfo/rmf-dev