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 for Python 3.11 #1099

Closed
11 tasks done
Thrameos opened this issue Oct 27, 2022 · 6 comments
Closed
11 tasks done

Release for Python 3.11 #1099

Thrameos opened this issue Oct 27, 2022 · 6 comments

Comments

@Thrameos
Copy link
Contributor

Thrameos commented Oct 27, 2022

  • Start from the release branch
    git checkout release
  • Make a new branch for the release cycle
    git checkout -b releases/{version}
  • Merge the current master with the release
    git pull origin master
  • Start a release
    bumpversion release
  • Edit doc/CHANGELOG.rst
  • Send the release to be evaluated
    git push
  • Verify CI on azure
  • Manually trigger a jpype.release on azure
    If successful, download the artifacts for publication.
  • Advance the release pointer
    git checkout release
    git merge releases/<version>
  • Publish the release
    • Add draft release on github
    • Attach the artifacts to the release.
  • Start master on a new cycle
    • Use a PR to pull release back to master
    • git checkout master
    • git checkout -b cycle
    • git merge release
    • bumpversion patch
    • Use PR to insert the cycle in master
@Thrameos
Copy link
Contributor Author

@marscher Not sure how many tries I will have to take for this release. There appears to be a problem with some of the the pinned versions not working with Python3.11. Hopefully unpinning them will work. If not I will have to come up with a new testing solution.

@Thrameos
Copy link
Contributor Author

Looks like the release will clear. I should be able to release tomorrow morning.

@Thrameos
Copy link
Contributor Author

It appears that the linux image does not have 3.11 available. I can distribute the rest and then try to get those built later.

@Thrameos
Copy link
Contributor Author

@marscher It seems like we need to change to manylinux2014 image to get Python 3.11. I can change to this for all future builds. But for now I am just updating the release script for a one off run. I am not sure if I need to split the build so that pre 3.11 goes with the manylinux2010 image. If you have some insight I can get it setup for our future releases.

Assuming everything looks good, the ball is in your court to push this to PyPi. Given the level of changes required for 3.11, I don't think one day after the release is too bad given that we have to wait for the azure image to be updated before we can release.

@marscher
Copy link
Member

Thanks! PyPI push of wheels and source dist has been done.

@marscher
Copy link
Member

Conda-forge support for 3.11 will be added by their bot soon. It has to pick up the PyPI push first.

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

No branches or pull requests

2 participants