Test 6.0 on Python 3.9 instead of 3.8.

[mauritsvanrees]

Python 3.8 is out of security support, so I will officially drop it from Plone 6.0 soon. As we say in the release schedule: "Plone 6.0 works on Python 3.8, but this Python version reaches end of life in October 2024. At that point, Plone 6 will drop support for Python 3.8."

We don't want to explicitly break it, so definitely no requires_python=">=3.9". But I am not going to take care of version pins for 3.8. If someone wants to keep using it on 3.8, it is there responsibility to keep their own version list.

While updating versions for 6.1 I already saw one or two that dropped support for 3.8. I will be updating the 6.0 versions soon too, so then it would be better if Jenkins tests 6.0 on 3.9 instead of 3.8.

This PR has a few other Python updates. I think I have it correctly, but please check. :-)

[gforcada]

LGTM!

Thanks, I will deploy them right away

[gforcada]

There is some extra tasks to be done after this merge:

• deploy the changes
• update mr.roboto mapping
• update jenkins.plone.org main tab and remove/disable old jobs

Do I miss anything? 🤔

[gforcada]

The mr.roboto update:

py_versions = {'5.2': ['2.7', '3.8'], '6.0': ['3.9', '3.11'], '6.1': ['3.10', '3.12']}

@mauritsvanrees are those the right combinations?

[gforcada]

@mauritsvanrees I took the liberty to create a Plone 5.2 view, so we can remove them from the Core view. I guess not so many contributors will miss it 😅

[gforcada]

Jenkins views updated as well 👍🏾

[mauritsvanrees]

The mr.roboto update:

py_versions = {'5.2': ['2.7', '3.8'], '6.0': ['3.9', '3.11'], '6.1': ['3.10', '3.12']}

@mauritsvanrees are those the right combinations?

Thanks for following up, Gil! Also thanks for moving the 5.2 jobs to a different view. As long as it is reasonably doable to keep those jobs, it is nice, so we can still run tests if needed for the odd change. If it takes too much effort, we can also drop them, as 5.2 is not supported anymore.

These mr.roboto combinations are for which PR jobs get started, right?
I think the minimum versions are good. For 6.0 and 6.1 we can debate which maximum versions to test with. The mr.roboto configuration now matches the Jenkins Core view, so that is good.

What we could change:

• Test 6.0 on 3.9 and 3.12.
  • Have only those two on the Core view.
  • Configure mr.roboto to create PR jobs for those two Python versions.
  • Make sure 3.10 and 3.11 are on the Core schedules view.
  • I expect that soon we can claim that 6.0 supports Python 3.13 as well. At that point we could add 3.13 to Core, let mr.roboto create PR jobs for that, and move 3.12 to Core schedules. We can also wait with changing anything further until this is the case.
• Test 6.1 on 3.10 and 3.13.
  • Have only those two on the Core view (currently we have 3.10, 3.12 and 3.13).
  • Configure mr.roboto to create PR jobs for those two Python versions.
  • Make sure 3.11 and 3.12 are on the Core schedules view.