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.

Sign up for GitHub

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

Jump to bottom

Document the structure of our release number #12780

Merged
merged 1 commit into from
Jun 21, 2024
Merged

Document the structure of our release number #12780

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/html/development/release-process.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,10 @@ that month will be up to the release manager for that release. If there are
no changes, then that release month is skipped and the next release will be
3 months later.

The version number of pip is ``YY.N``, where ``YY`` is the year of the release
and ``N`` identifies which release of the year (0=January, 1=April, 2=July, and
3=October).
Comment on lines +22 to +23
Copy link

Choose a reason for hiding this comment

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

@pfmoore If I trust PyPI, pip 24.0 was released in February and pip 24.1 in June, which doesn't quite match what you've written here, so perhaps it would be better to be less specific ? 😁

Copy link
Member Author

Choose a reason for hiding this comment

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

The releases are the ones quoted in the existing paragraph above. They are described using the intended month of release but yes, we do slip sometimes (rather more often than would be ideal, but we're highly limited in resources). The problem with being less specific is that if we decide to skip a release (for example, the July release, as we've only just released 24.1) people would get equally confused that we had 24.0, 24.1 and 24.3 but no 24.2.

This is a compromise, to get the idea across without being over-complicated.

Copy link
Member

@pradyunsg pradyunsg Jun 21, 2024 •
edited
Loading

Choose a reason for hiding this comment

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

It might be clearer to refer to them as quarters of the year?

Copy link
Member Author

Choose a reason for hiding this comment

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

That would work, yes.

Copy link
Member Author

Choose a reason for hiding this comment

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

How does #12783 look?


The release manager may, at their discretion, choose whether or not there
will be a pre-release period for a release, and if there is may extend that
period into the next month if needed.
Expand Down
Loading