Am 07.07.2013 20:06, schrieb Jeroen De Dauw:
Any objections against starting work on this next week (ie the one that starts tomorrow)? (Do read my original mail (below) first in case you have not yet already done so.)
I'd like to first discuss the implications for deployment for the foundation. Basically, one repo per component is better for testing and "managed" installation, but problematic for deployment and manual installation, as well as for development/code review.
A separate extension for each component means maintaining a lot of compatibility info somehow, somewhere. This is an issue for people installing by hand (yes, composer should help with that) and is a pain for development (there's a major refactoring of the formatter/parser stuff imminent).
I'd like to think about cost v.s benefit again. Why exactly should we do this? And what can we do to make it less of a pain?
Maybe having the components as submodules, instead of separate extensions, would help... Something to ask the Foundation.
-- daniel