Skip to content
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

Add more detailed versioning policy #197

Merged
merged 2 commits into from
May 26, 2023
Merged

Conversation

JelleZijlstra
Copy link
Member

In particular, introduce a release candidate phase.

Fixes #185

@srittau
Copy link
Collaborator

srittau commented May 26, 2023

I would personally only do rc releases if existing functionality changes. When a release only contains new classes and functions (for new PEPs etc.), regressions are very unlikely. But as you are the RM I am happy with any policy that you are happy with.

Copy link
Collaborator

@srittau srittau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See my comment above, but I am also fine with this.

@JelleZijlstra
Copy link
Member Author

I think it's useful to do for new features too (e.g., there was a bug in @deprecated that we fixed this week), and in any case recently we've made a lot more changes to existing functionality than adding new stuff.

@srittau srittau merged commit 0d453f5 into python:main May 26, 2023
@JelleZijlstra JelleZijlstra deleted the versioning branch May 26, 2023 18:51
JelleZijlstra added a commit that referenced this pull request Jun 1, 2023
@JelleZijlstra JelleZijlstra restored the versioning branch September 10, 2024 23:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use pre releases to allow community find bug or patch its packages.
2 participants