the title says it all, so TL;DR: I would like to integrate the Neos.Ui into our neos-development-collection for the next major release (Neos 6.0).
I haven’t really thought it through yet, but I think this would greatly simplify our core development and release process.
One risk I see is that we create a tighter coupling this way by accident¹.
But if we’re careful it can even ease the process of untangling the two worlds. For example we could replace the UI routes at once and avoid PRs that depend each other²
Another consequence would be version numbers that stay in sync – or to put it less positive: We’d have to create a new Core Release if only the UI needs an update vice versa.
I don’t think that this is an issue, either. We usually wait with releases anyways until a couple of new fixes/features are merged (except for critical bugfixes of course).
But before I get more into it – I think that we discussed that before and maybe there are really good reasons against going this route.
¹ The UI repositories would still exist but be turned into readonly mode like the other subsplit packages. that way we could push changes to the Neos “backend” and the UI parts simultaneously thus making it easier to blur the line
² We have that all the time today (see https://github.com/neos/neos-development-collection/pull/3013) for example