mistercrunch opened a new pull request, #27906:
URL: https://github.com/apache/superset/pull/27906
### SUMMARY
In this PR:
- simplifying the single-item matrix (python-version) to NOT using a
matrix. I'm guessing the reason we currently have a single-item matrix
is an artifact of supporting multiple version in the past, and/or making it
easy to go multi-python-version checks in the future, but there's a burden
associated, especially around how this relates to "required checks"
specified in .asf.yml
- leveraging the `setup-backend`'s default for python version, making
the main python version we use much more DRY.
- fixing/simplifying the related no-op workflows. We'll need new ones, but
will
be able to deprecate a bunch and simplify things. For instance,
when we migrate to 3.11 in the future, we won't have to manage
a bunch of python-version-specific no-ops
About supporting multiple/future version of python, I'd argue that we
should focus on a single one for a given CI run, and that if/when we
need to CI against multiple version, we run a FULL test suite
punctually in a dedicate PR/branch/ref. Point being, it's expensive
for every commit to validate multiple versions of python and in
many ways its not necessary.
Currently our multi-python-version support is dubious at best, with only
few checks that run against multiple versions. I really think
we should pick a single version and support it very well. If/when we
want to upgrade python version, we'd cut a PR and run CI for that
purpose.
If we want to continuously, actively support multiple python versions
(and I don't think we should!), I'd suggest either
a release-specific procedure (release manager using
release branch, running full CI for that version/release) and/or a
nightly job that would keep an eye on that version of python.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
