Thanks @james for pointing this put.
To me a breaking change is “something that changes the CMS that gets included in core”.
It doesn’t mean that the change will surely break sites.
It seems instead the term is used literally to mean that this kind of changes are going to break sites FOR SURE because even if we are carefully introducing them it is impossible to make them safe.
My question then is: why should someone risk all their site to upgrade to V2 from v1, when there’s no certainty? Only for the sake of new features? It’s not much different from what WP did with block editor. It’s only slower and gradual. But in the end, the result might be the same. Sites being broken nevertheless.
@joyously thanks for explaining WP autop better, not being a dev I clearly misunderstood when trying to piece together what the issue with it is.
About the “where is this written”, there were many discussions (slack and forums) and what I understood is that people were working to make things happen in a certain order. There wasn’t a real “let’s write this up officially” but the fact people discussed the possibility to release the editor in core during version 2 to me means that the community leans towards that solution at present. What I noticed is that the project is progressing when people take leadership and tends to stall when this leadership “vanishes”, but the general direction is to release things one after the other. Not at the same time. Directory is at the final stages and people are pushing to put it in core when ready, but being the editor important I believe the suggestion to include it in the V2 cycle is consistent enough to call it a plan.
Other people stated that CP doesn’t seem to have a “real plan”, that the roadmap isn’t really a plan.
I think the real plan may not be the official written one because some people may not recognize themselves into it, but it is surely represented by what people get done. I mean… If many people work on something like the directory for many hours this means they want it and they “see it in core”. Things like the directory and the editor really received constructive discussion that lead people to actively DO SOMETHING. Even if there were conflicts, disagreements and misunderstandings along the way. These two things and what is going into V1 point releases are the real plan. These things are being worked on. Are what people see when coming to meet CP for the first time.