Affects Version/s: None
Fix Version/s: None
The "core-main-contrib-playground" structure that emerged over time tends to clutter the git history a lot, and is becoming more annoying than helpful. Sebastian wrote a nice document summarizing his "reform" ideas:
There are several aspects to this problem, hence I create this epic to collect issues discussing them.
Let me try to summarize the problems of the current approach:
- the history consists mainly of playground-related changes, making it more difficult than it should be to track the changes in main/core. In particular, it makes it difficult to create release-to-release exhaustive changelogs
- even though it is provided as a service, refactoring of code in playgrounds is often lived as an annoyance (one could argue it is the playground's users fault, but I think the problem is more how the concept of playground got transformed over time)
The way forward would be to be more confident in our releases, and get rid of contribs and playgrounds from the main repository — where we could impose a strict commit policy, and make more extensive use of branches.
This would be quite a dramatic change, so I think we need to allocate sufficient time for discussing this at the developer meeting. I will link existing and new issues to this epic to get the discussion started before September. Feel free to create more issues.