devguide icon indicating copy to clipboard operation
devguide copied to clipboard

Provide guidelines for backporting

Open ned-deily opened this issue 6 years ago • 1 comments

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.

ned-deily avatar Jul 01 '19 22:07 ned-deily

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

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

hugovk avatar May 03 '23 14:05 hugovk