Right now, for a given release, CHANGES.md starts with a “Breaking Changes” section followed other changes in random/time order. I suggest, we order it like:
- Breaking changes
- New features
- Bug fixes
- Misc - third-party libraries, data changes, etc.
This is how b13 is currently organized. The idea is to the most important things are first and we are upfront about breaking changes.
The ordering is something that needs to holdup a pull request, but the person doing the release should double-check it and tweak as needed.