Where to log breaking changes for Master releases

[JorySchossau]

This is a reminder for us to discuss at the next meeting.

[JorySchossau]

We decided in the weekly meeting:

• Master releases will have a public relations step where we create a "blog post" describing a handful of showcased new features and describe them, a paragraph or more each. Then a slightly cleaned up trimmed list of changes from the commit history (of feature pull requests).
• Breaking changes were defined as those that if a user were to paste in their module from the previous version of Master, would
• • cause compiler error
• • cause a runtime error/crash
• • cause unexpected behavior change, such as interpreting a loaded genome differently
• breaking changes Pull Requests should be given the Breaking label, and described briefly in the PR description.