Consider doing "-rc" releases on PyPI

[cbm755]

I think before 1.22.0, there might've been a 1.22.0-rc (?) At least I think I saw references to that in the docs.

But I don't think it ever appeared on PyPI. It seems it is possible to "tag" a pre-release on PyPI for wider testing. Maybe that would be a good idea in the future?

Here's an example for Pandas: https://pypi.org/project/pandas/#history

---

I think (but haven't tried it myself) that users would then be able to install with pip install --pre pymupdf

[cbm755]

oh, in fact this was done in the past: https://pypi.org/project/PyMuPDF/#history

In that case, it was likely just overlooked for the latest release: maybe this should be bug, not an request for enhancement?

[julian-smith-artifex-com]

We decided not to use release candidates for 1.22.0. Please open a Discussion if you want to talk more about this.

[JorjMcKie]

I allow myself to add that a qualification as "bug" would be pointless, because it were impossible to fix it.

[cbm755]

@JorjMcKie I did mean "for future releases", not backwards in time ;-)

@julian-smith-artifex-com Sure, we can move it to discussion: I don't see button to do that, perhaps you can?

My $0.02 for that discussion: if you'd had a -rc, I might've run my test suite against it and we'd have caught #2348 before release. (Of course I might not have gotten around to it! But perhaps I can tool my CI to run a pip install --pre pymupdf job for example.)

[cbm755]

@JorjMcKie "bug" in the sense of "Your CI/CD for 'rc' tags is not pushing to PyPI".