+1 Anton. We've included it in the new simplified Github PR template that has a chance to actually be treated as checklist :) See the description here: https://github.com/apache/airflow/pull/955 .
And after some thoughts I am also ok with adding the comment in UPDATING.md by Kamil where people should provide more information (see below). I think that's good if we can add more information and we should also update the existing descriptions there. <!-- I'm glad you want to write a new note. Remember that this note is intended for users. Make sure it contains the following information: - [ ] Previous behaviors - [ ] New behaviors - [ ] If possible, a simple example of how to migrate. This may include a simple code example. - [ ] If possible, the benefit for the user after migration e.g. "we want to make these changes to unify class names." - [ ] If possible, the reason for the change, which adds more context to that interested, e.g. reference for Airflow Improvment Proposal. More tips can be found in the guide:https://developers.google.com/style/inclusive-documentation --> J.
