[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [rmf-dev] proposal for simplifying git repository structure
|
Am 27.01.2012 18:19, schrieb Michael Jastram:
Dear all,
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
Labs):
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
make sense?
... 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 [1]. 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
rif12).
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
anyway.
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?
My desire for that is strong ;-)
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
I suggest to have separate repositories for product code, incubation
and deprecation.
This is certainly something to consider once we leave incubation. For
now, I don't think this is necessary.
Best,
- Michael
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=345471
