I think we are decided that the NodeTypes package(s) are not really best practice and we want to get them out of the “default” package set. To that end we should extract them from the dev collection. I think that’s an OK breaking change to the collection as the single packages do not break at all.
That’s the first point I wanted to gather feedback on. Do you feel it’s ok to “break” dev collection in that way? If someone installs dev collection and relies on the NodeTypes package they should have declared it a dependency and it would just be pulled separately, so that should be fine still…
Secondly as the inline editor config changed it should be adapted in the NodeTypes package. As both configs do not work together and are not compatible, this is definitely a breaking change to the package, but also something you definitely want for newer projects with the NodeTypes packages. So therefore I would suggest that right after extracting them (or lets say aligned with the upcoming release) we split a 4.1 branch (in line with the upcoming Neos release) and then immediately merge the chnage for new configuration to master and make it 5.0 so that this package has a higher version number than the rest of Neos but you as integrator have a concious choice of new or old configuration.
That’s the second thing I wanted feedback on, does that sound sensible to you? Any objections to this plan?