Page History

...

Since the goal is a stable master, bugfix PRs should go to master first. This way we make sure all upcoming releases have the fix included.
Then we should decide if the fix should go to other release branches as wel. It could be that the same patch on master can be applied to the release branch (plan A). Or else that the fix needs to reimplemented / back ported due to refactoring (or similar) on master (plan B).
When we get a PR that is not against master, we should be extra careful. We should ask people to specify why they want to do this as there could be a valid reason, of course. The danger is forgetting to apply it to master as well, in which case we'll be introducing old bugs again if people upgrade later on. We should prevent that from happening.

Image Added

Which releases to maintain?

...