Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Delete python 2.7 jobs? #350

Closed
gforcada opened this issue Mar 3, 2024 · 2 comments
Closed

Delete python 2.7 jobs? #350

gforcada opened this issue Mar 3, 2024 · 2 comments
Assignees

Comments

@gforcada
Copy link
Sponsor Member

gforcada commented Mar 3, 2024

On the release schedule it says that Plone 5.2 is only supported for Python 3.8 until late this year (2024), but that Python 2.7 is only meant to be used as a stepping stone to move to Python 3.8.

Given that, do we want to keep the Jenkins jobs for Python 2.7 for Plone 5.2? Or can we remove them already? 🤔 Or a middle ground: move them to a Core Schedule, i.e. run them once a week.

@mauritsvanrees
Copy link
Sponsor Member

No, please keep testing on 2.7. It is easy for something to break here unnoticed if someone commits a PR and only tests it on Python 3.
There is not much happening on 5.2 anymore, so the tests probably already run less than once a week.
If it helps, we could restrict the 2.7 jobs to be run only on for example Node 1, so that other Nodes do not need Python 2 anymore. But I suspect this would make the setup actually harder.
BTW, I probably want to do one last 5.2 release this spring, even though it is technically out of maintenance.

@gforcada
Copy link
Sponsor Member Author

Sure, all good 👍🏾

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants