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

Release 22.0 #10726

Closed
pradyunsg opened this issue Dec 12, 2021 · 29 comments · Fixed by #10841
Closed

Release 22.0 #10726

pradyunsg opened this issue Dec 12, 2021 · 29 comments · Fixed by #10841
Assignees
Labels
type: maintenance Related to Development and Maintenance Processes

Comments

@pradyunsg
Copy link
Member

We're about three weeks out from a new year! I guess we'd want to cut a 22.0, given how full that milestone is. :)

@pradyunsg pradyunsg added this to the 22.0 milestone Dec 12, 2021
@pradyunsg
Copy link
Member Author

I can pick this up, although I won't be around during early Jan (I'm on vacation!); so the only time I would be able to do anything about these would be sometime in mid-Jan/late-Jan.

@pradyunsg pradyunsg added the type: maintenance Related to Development and Maintenance Processes label Dec 12, 2021
@pfmoore
Copy link
Member

pfmoore commented Dec 12, 2021

Sorry, I really don't want to commit to doing the January release, as I'm likely to be pretty busy. Hopefully I might have more free time later in the year to help out with the releases.

@mattip
Copy link
Contributor

mattip commented Dec 14, 2021

Is there a documented process to update _vendor? It would be nice to get packaging 21.0 -> 2.13.

@pfmoore
Copy link
Member

pfmoore commented Dec 14, 2021

It's covered in the documentation. However, I think we have a nox session for that - nox -s vendor.

We do a pass updating all of our vendored libraries just before a release anyway, so this should get caught then.

@uranusjr
Copy link
Member

I won’t be around in earlier January either (actually will likely not be around starting from later December).

@pradyunsg
Copy link
Member Author

Yea, and it should be possible to run the vendoring nox session with an upgrade flag, which automatically tries upgrading things; stopping when a failure occurs in the upgrade process.

@pradyunsg
Copy link
Member Author

I'm gonna pre-emptively assign myself then. :)

If there's any concerns of any other committer wants to step up, just say so. :)

@pradyunsg pradyunsg self-assigned this Dec 14, 2021
@pradyunsg pradyunsg pinned this issue Jan 4, 2022
@pradyunsg
Copy link
Member Author

these would be sometime in mid-Jan/late-Jan.

Cool, this is the plan for the release now.

@pradyunsg
Copy link
Member Author

pradyunsg commented Jan 26, 2022

@pypa/pip-committers Okay, there's a few PRs that I'd like reviews on.

I think there's agreement on those ideas overall, but... more eyes, a proper review and an easy green tick 🤞🏽 would be much appreciated! I'm leaning toward merging those anyway tho, if there's no availability to do a review.

@pradyunsg
Copy link
Member Author

Alrighty, looks like we're all set. I'll cut a release over the weekend. :)

@pradyunsg pradyunsg linked a pull request Jan 30, 2022 that will close this issue
@pradyunsg pradyunsg reopened this Jan 30, 2022
@pradyunsg
Copy link
Member Author

sigh Why is GitHub like this.

@pradyunsg pradyunsg modified the milestones: 22.0, 22.0.1 Jan 30, 2022
@pradyunsg
Copy link
Member Author

Alrighty. There were a couple of bugs in the html5lib transition logic, so... I'll cut 22.0.1 sometime later today/this week.

@Jonamaita
Copy link

Hi !!

I am trying use pip-compile with this release. But, when i try compile i get a AssertionError.

lib/python3.8/site-packages/piptools/repositories/pypi.py", line 455, in _setup_logging
    assert isinstance(handler, logging.StreamHandler)
AssertionError

Maybe I'm missing something?.

@pradyunsg
Copy link
Member Author

You might want to file an issue against https://github.com/jazzband/pip-tools. That looks like a bug on their end -- they're using pip's internals (something that is not supported) and quite possibly they weren't prepared for #10461. :)

@hugovk
Copy link
Contributor

hugovk commented Jan 30, 2022

It's been reported at jazzband/pip-tools#1558.

@mattip
Copy link
Contributor

mattip commented Jan 30, 2022

Does it make sense to try release candidates for future releases? It makes the release process more complicated, but it might allow people to try out the new version before commiting to a release.

@pradyunsg
Copy link
Member Author

Released 22.0.1 now!

@pradyunsg
Copy link
Member Author

@mattip We've done those before, but our experience is that not enough users test them; even when we've done a round of publicity about the release.

@pradyunsg
Copy link
Member Author

Working on the CPython PR.

Gonna defer this for next weekend. 🙈

@pradyunsg
Copy link
Member Author

22.0.2 is out on PyPI and get-pip.py has been updated. :)

@mattip
Copy link
Contributor

mattip commented Jan 30, 2022

Thanks for all the work!

@pradyunsg pradyunsg removed this from the 22.0.1 milestone Jan 30, 2022
@zooba
Copy link
Contributor

zooba commented Jan 31, 2022

@pradyunsg Should there be a 22.0.2 tag in the repo?

@pradyunsg
Copy link
Member Author

pradyunsg commented Feb 1, 2022

@pradyunsg Should there be a 22.0.2 tag in the repo?

Yea... I'd accidentally pushed to my fork instead of this repository. Fixed that in the morning (UK). 😅

@pradyunsg
Copy link
Member Author

22.0.3 is out, w/ a get-pip.py upgrade.

@klalumiere

This comment was marked as off-topic.

@notatallshaw

This comment was marked as off-topic.

@klalumiere

This comment was marked as off-topic.

@pradyunsg
Copy link
Member Author

Please file a separate issue for this, as a bug report. This specific issue is for coordinating the release amongst the maintainers and contributors.

@pradyunsg
Copy link
Member Author

Released the (hopefully, final!) 22.0.4 bugfix for this release.

If there's a security fix needed, I'm happy to cut it out of band -- until we decide on a 22.1 release manager in April. :)

richarms added a commit to ska-sa/katsdpcontimh that referenced this issue Mar 16, 2022
@pradyunsg pradyunsg unpinned this issue Mar 18, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: maintenance Related to Development and Maintenance Processes
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants