gh-109408: Azure Pipelines: test 3.12 branch

[hugovk]

As noted in #109408 (comment), Azure Pipelines CI (ci.yml) runs tests on version branches post-merge.

But it's only running on main and 3.11 and older, and not on 3.12, because we forgot to add it when branching 3.12 from main in May:

Screenshot

Also, Azure Pipelines PR (pr.yml) only runs for PRs to main, but I added the missing 3.12 anyway (and am planning on eventually removing it in #109408):

Screenshot

Should we remove 3.7 from these lists?

• Issue: Move Azure Pipelines CI to GitHub Actions #109408

[vstinner]

It should be added to PEP 101 release process to not forget it next time.

[hugovk]

It should be added to PEP 101 release process to not forget it next time.

Looking at PEP 101, should it be added to https://github.com/python/release-tools/blob/master/release.py?

• Bump version numbers via the release script:
  $ .../release-tools/release.py --bump X.Y.ZaN

[vstinner]

I didn't understand well the future of Azure Pipelines. If it goes away, updating the release tool is not needed.

[hugovk]

There are two Azure Pipelines runs.

One for PRs (pr.yml) - we're planning on removing this one, it's the one most people would notice.

The other runs on version branches after merging PRs (ci.yml), and it's not visible in PRs. Steve would like to keep this one running to do some extra Windows packaging checks (#109408 (comment)), so that can stay.

[hugovk]

Apologies for the force push, it was a mistake! No changes to the PR other than rebasing on main.

[hugovk]

It should be added to PEP 101 release process to not forget it next time.

Looking at PEP 101, should it be added to python/release-tools@master/release.py?

• Bump version numbers via the release script:
  $ .../release-tools/release.py --bump X.Y.ZaN

Issue created: python/release-tools#56

[vstinner]

LGTM

[vstinner]

The other runs on version branches after merging PRs (ci.yml), and it's not visible in PRs. Steve would like to keep this one running to do some extra Windows packaging checks (#109408 (comment)), so that can stay.

Sure, it makes sense. Thanks for the explanation.

[miss-islington]

Thanks @hugovk for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12.
🐍🍒⛏🤖 I'm not a witch! I'm not a witch!

[bedevere-app]

GH-109535 is a backport of this pull request to the 3.12 branch.

[bedevere-app]

GH-109536 is a backport of this pull request to the 3.11 branch.