Skip to content

Provide guidelines for backporting #503

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ned-deily opened this issue Jul 1, 2019 · 1 comment
Open

Provide guidelines for backporting #503

ned-deily opened this issue Jul 1, 2019 · 1 comment
Labels

Comments

@ned-deily
Copy link
Member

ned-deily commented Jul 1, 2019

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
Copy link
Member

hugovk commented May 3, 2023

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

Related: #1069 asking about backporting docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants