On Fri, 1 Sep 2017 00:28:19 +0200, Emmanuel Bourg wrote:
Le 31/08/2017 à 23:33, Gilles a écrit :
it's a pity we cannot meet in person to sort all those issues
Hum, maybe with a few beers you'll be easier to convince ;)
It would quite probably require a stronger beverage.
I'm not against you modularizing CM, I'm against me doing it
just because you "think" it's a better approach to the
(management) problems which I've been describing for at least
two years (and some more).
I understand your point of view, you don't want to spent a lot of
time
modularizing CM, dealing with parts of the code you are not
comfortable
with and delaying the release of code you really care about. That's
fair
and I agree this shouldn't be forced upon you.
There is some truth, but not all of it.
For a long time, I'm viewing CM more from a maintainer's POV
rather than from a user's POV. IOW, the "prioritizing" I was
mentioning, in one of the suppressed parts of my preceding
message, is not based on what I "really care about", but on
how generally useful they are (hence my being convinced that
those would be good "Commons" component candidates).
The good news is you don't actually have to refactor *all* of CM as a
multi-module project right now. Start with a mostly empty branch
containing just a couple of modules you like and release them. And
you
progressively bring more modules after each release from the old CM
branch.
Does everyone agree with that? [I seem to recall having made
such a proposal, and it was not deemed acceptable...]
That's equivalent to the creation of multiple components (you
cherry-pick the code that you want, and release it when ready),
Because of "Commons" rules, it is not "equivalent": There was
a long thread concluding that all modules must be released
_together_, and with the same top-level package name and version
number.
It is very "maintainer(s)-unfriendly" because of the quite
different subject matters that coexist in CM.
and you
keep the lightweight management of a single component.
I think that the unspecified problem(s) which you refer to
here are mostly alleviated with tools such as git and maven.
The problems I referred to in the preceding paragraph can't
be. [Proof is the management crisis that ultimately doomed CM.]
Gilles
Emmanuel Bourg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
