python / devguide

The Python developer's guide
https://devguide.python.org/
Creative Commons Zero v1.0 Universal
1.86k stars 781 forks source link

Provide guidelines for backporting #503

Open ned-deily opened 5 years ago

ned-deily commented 5 years ago

The devguide currently gives information about how to do a backport of a fix from the feature (master) branch to maintenance branches but I see very little in the way of guidance on how to decide if a backport is needed. The question has come up with core developers not really knowing what our policy, resulting in either a potentially beneficial fix not reaching users until one (even two) feature releases have passed or a fix being sent out prematurely in current maintenance releases introducing risk or, worse, an unnecessary incompatibility.

hugovk commented 1 year ago

@JelleZijlstra has written some notes at https://jellezijlstra.github.io/cpython#backporting

Related: https://github.com/python/devguide/issues/1069 asking about backporting docs.