Skip to main content

[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 13:17, schrieb Mark Brörkens:
[...]

(1)
Current situation:
The RMF code is separated into 5 git repositories:
/gitroot/rmf/org.eclipse.modeling.rmf.core.git
/gitroot/rmf/org.eclipse.modeling.rmf.core.reqif10.git
/gitroot/rmf/org.eclipse.modeling.rmf.core.rif11.git
/gitroot/rmf/org.eclipse.modeling.rmf.core.rif12.git
/gitroot/rmf/org.eclipse.modeling.rmf.pror.reqif10.git
Yes, that's bad.


(2)
Some thoughts about the current repository structure:
* initial setup of the development environment takes some time
I'm willing to set up a Buckminster releng component that automatically materializes the sources in the workspace and the proper dependencies in a dedicated target platform. See http://wiki.eclipse.org/CDO_Source_Installation for an example.

* many development activities do not only affect a single repository. I often need to push to more than one repository.
   This takes time and overall consistency of the code needs to be ensured manually.
Yes, ideally we want something like an SVN trunk that you can simply checkout and immediately build without errors or warnings ;-)

* The repositories are quite small. Thus, there is no need (yet) to separate them due to performance or memory consumption reasons
Yes.

* Setting up automatic builds is more complex since the checkout procedure needs to be repeated for each repository
Yes.


(3)
Proposal:
I think we should merge the current repositories into a single new repository and remove the old repositories.
/gitroot/rmf/org.eclipse.rmf.git
I suggest to have separate repositories for product code, incubation and deprecation. See http://git.eclipse.org/c/cdo for an example.


(4)
Further reading and thoughts about repository granularity can be found at
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=345471
      (In short: it is a good practice to have a single repository per project)
[2] http://git.eclipse.org/c/
      (an overview over existing git repositories)
That only helps if we understand *why* projects have chosen their approaches ;-)


(5)
Does anybody know how to merge git repositories?
It is important that the change history is merged into the new repository.
I have no clue ;-(

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper






_______________________________________________
rmf-dev mailing list
rmf-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/rmf-dev




Back to the top