Ready for 3.6.0 full PyPI/GitHub release

[sbillinge]

PyPI/GitHub full-release preparation checklist:

• Create a new conda environment and install the rc from PyPI (pip install <package-name>==??)
• License information on PyPI is correct.
• Docs are deployed successfully to https://www.diffpy.org/<package-name>.
• Successfully run all tests, tutorial examples or do functional testing.

Please let @sbillinge know that all checks are done and the package is ready for full release.

conda-forge release preparation checklist:

• Ensure that the full release has appeared on PyPI successfully.
• New package dependencies listed in conda.txt and test.txt are added to meta.yaml in the feedstock.
• Close any open issues on the feedstock. Reach out to @bobleesj if you have questions.
• Tag @sbillinge and @bobleesj for conda-forge release.

Post-release checklist

• Run tutorial examples and conduct functional testing using the installation guide in the README. Attach screenshots/results as comments.
• Documentation (README, tutorials, API references, and websites) is deployed without broken links or missing figures.

[yucongalicechen]

The version shows up correctly and functions work.

[sbillinge]

I did a 3.6.0rc1 release to try and trigger the doc building workflow, but for some reason I don't think it ran? @bobleesj ?

[bobleesj]

Yes, replied here #308 (comment)

but prob it's better to communicate here moving forward

[sbillinge]

@yucongalicechen NO need to build an env and test rc1 or higher.....this was just to try and test the pre-release doc bulid. But we do want to build and look at the docs before doing the full release...

[sbillinge]

ok, I pushed rc2. @bobleesj , how do we access the docs when they are deployed? Do they just deploy to the usual github.io place or is there a special rc place?

[bobleesj]

Do they just deploy to the usual github.io place or is there a special rc place?

Yes, the current setup just deployed to the main URL. diffpy.github.io/diffpy.utils

I pushed rc2

Dang it, the GitHub doc workflow CI isn't triggering on rc2.

@sbillinge

I will need to fix and test this with a dummy org/repo. Dinner time soon... maybe continue tmr morning or sth? hopefully you can push a tag or merge on the train?

[bobleesj]

Do they just deploy to the usual github.io place or is there a special rc place?

Maybe we need a better instruction on this in the checklist. Should we later look into deploying a separate URL for rc versions? Maybe? For some packages (pdffit2...) may have a delay between rc release and full release.

[sbillinge]

Do they just deploy to the usual github.io place or is there a special rc place?

Maybe we need a better instruction on this in the checklist. Should we later look into deploying a separate URL for rc versions? Maybe? For some packages (pdffit2...) may have a delay between rc release and full release.

No, let's keep it simple. If there is a big boo boo and we want to revert the docs we can just rerun the previous full release version with workflow_dispatch or sthg.

[sbillinge]

Do they just deploy to the usual github.io place or is there a special rc place?

Yes, the current setup just deployed to the main URL. diffpy.github.io/diffpy.utils

I pushed rc2

Dang it, the GitHub doc workflow CI isn't triggering on rc2.

@sbillinge

I will need to fix and test this with a dummy org/repo. Dinner time soon... maybe continue tmr morning or sth? hopefully you can push a tag or merge on the train?

OK, sounds good. Signing off for tonight. I should have enough bandwidth tomorrow to do it.

[bobleesj]

@yucongalicechen a quick Q. Do you have access to check off items in the issue checklist? I am asking since this issue is created by @sbillinge

[bobleesj]

@sbillinge saw 3.6.0rc3 released

Seems all good with doc showing the latest github tag as expected

[bobleesj]

@sbillinge Time for 3.6.0 full release. Let's see if we have Release Notes displaying 3.6.0 and 3.6.0 tag commit equal to that of main..

[sbillinge]

I will put a shift in on the docs now before we do the full release. Give me an hour or so.