I have no idea how it impacts anything, but keep in mind that framework
releases regularly (and generally) include more than one subproject. I
don't know how it complicates anything, just wanting to point it out. In
other words, it would be nice if those pushing this make sure they work
out all of the ramifications for all subprojects in advance, since they
are fixing something that isn't broken.
-> richard
On 10/27/15 08:11 , Oliver Lietz wrote:
On Tuesday 27 October 2015 11:26:37 Carsten Ziegeler wrote:
Am 27.10.15 um 11:12 schrieb Benson Margulies:
My recommendation at this point in the discussion is to convert the
repo _en bloc_, then split out very independent things (if any), and
only then contemplate add-ons.
I think we should split up from the beginning. We can split up by
functional blocks, or we clearly identify a number of things where we
already know today that it would make sense to keep them in a single
repository.
Personally, I would put every artifact which is released in a single git
repo. It's a one time conversion from svn to git and with all the
different tooling available ,dealing with several git repos is not that
difficult. But of course different people think and work differently, so
I guess going with a compromise is the best option.
+1 for a repo per release artifact. Simple rule and simply works best™.
O.
Carsten
