Schedule release for 1.6

[Thrameos]

@marscher i have a large number of items on the burner, but I also have requests for a maintenance release. I will be starting the release scripts for 1.6 next Wednesday and pushing all outstanding tasks to 1.7. If there is anything that seems like it should be included (i don't see anything in that category) then we should merge it.

[marscher]

I agree with your plan. Please go ahead.

[Thrameos]

Still running a bit behind. Heavy work weeks.

[Thrameos]

• [x] Start from the release branch git checkout release
• [x] Make a new branch for the release cycle git checkout -b releases/{version}
• [x] Check the .azure scripts to see if they are up to date. Look on https://devguide.python.org/versions/ to see what versions can be dropped Check Python versions for Windows Check Python versions for OSX Check the manylinux image for Linux
• [x] Merge the current master with the release git pull origin master
• [x] Start a release bumpversion release
• [x] Edit doc/CHANGELOG.rst
• [x] Send the release to be evaluated git push
• [x] Verify CI on azure
• [x] Manually trigger a jpype.release on azure If successful, download the artifacts for publication.
• [x] Advance the release pointer git checkout release git merge releases/<version>
• [x] Publish the release
  • Add draft release on github
  • Attach the artifacts to the release.
• [x] 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]

FIXME add directions for checking manylinux to release instructions FIXME add a requirements file for release in .azure to make it easier to conduct a release. FIXME move the doc/CHANGELOG checks earlier in process. FIXME pointers to azure locations would help

[Thrameos]

Going to take a while.... arm4 is very slow to run (likely being emulated) and the number of items in the manylinux build have expanded. I am currently hitting CPU limits on azure cloud. Will try to resolve but gad it is slow.

[petrushy]

Many thanks for this release!

Just a heads-up as I don't see it on the list - pypi package needs an update as well

[Thrameos]

@marscher handles that portion and the anaconda update.

[tnaroska]

Just seeing this thread. Is there any chance of the 1.6 release getting pushed to pypi? @marscher @Thrameos Thanks!

[pelson]

@marscher & @Thrameos: Given the azure pipeline does the wheel building, is there any reason not to setup trusted publisher releases to PyPI, so that it ends up there automatically on git tag?

[Thrameos]

It would take another script to do the push. Just because release completes doesn't necessarily mean it is ready to push.

Unfortunately I don't have the keys to make the push to pypi nor kick off the anaconda builds. If marsher can't do it we will need to set up a backup maintainer.

[petrushy]

@marscher sorry to bother, but a kind reminder. it would be very nice to get this release to pypi & conda. The current conda is fetching source zip from pypi, but that could be changed to the github so there isn't a dependency there and that could move forward - seems to be more people admin on conda.

Update: started on a MR on jpype1-feedstock for the conda package (based on github release) at https://github.com/conda-forge/jpype1-feedstock/pull/57

[marscher]

Sorry for the delay. It is summer time and I was on vacation (Europeans do this shit once a year at least).

[pelson]

@marscher glad to hear it! 🌞😎

Do you want to share the load for the future? e.g. using the PyPI trusted publishers workflow, or adding other maintainer on pypi?

[marscher]

I'd be totally fine with adding another PyPI maintainer. Honestly I do not trust the "trusted" publishers. I'd prefer to test the source wheel prior pushing it.

If you wish to volunteer just give me your PyPI username. Thanks a lot!