You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of now, we run tests only for the latest and oldest supported python and Django versions. This might not be ideal in every case, because something that might work on Django 3.2 doesn't necessarily work on 3.1 because 3.2 is LTS(long term support) so patches are still back ported to it. Whereas 3.1 is in freeze mode and hence it does no longer receive back ports.
Similarly, for 2.1 and 2.2(LTS).
In order to not get caught in a situation where a test failure wouldn't be caught by our test suite, I think we should run them on all supported python and Django versions. I understand that we had made this choice to run only on some versions earlier to reduce the testing time. A lot on this front has been taken care now that tests run in fairly less amount of time and tests for different versions can be run parallelly(if this is not true on travis, maybe we can switch to GitHub actions).
Also, i found that we don't run the tests on Django 3.2 on travis, this was probably missed in e171d8f. This too can be handled in this.
Change Type
[ ] Refactor/Enhancement
[ x] Testing
[ ] CI/CD
[ ] Other
Proposed Changes
As of now, we run tests only for the latest and oldest supported python and Django versions. This might not be ideal in every case, because something that might work on Django
3.2
doesn't necessarily work on3.1
because3.2
is LTS(long term support) so patches are still back ported to it. Whereas3.1
is in freeze mode and hence it does no longer receive back ports.Similarly, for
2.1
and2.2
(LTS).In order to not get caught in a situation where a test failure wouldn't be caught by our test suite, I think we should run them on all supported python and Django versions. I understand that we had made this choice to run only on some versions earlier to reduce the testing time. A lot on this front has been taken care now that tests run in fairly less amount of time and tests for different versions can be run parallelly(if this is not true on
travis
, maybe we can switch to GitHub actions).Also, i found that we don't run the tests on Django
3.2
on travis, this was probably missed in e171d8f. This too can be handled in this.This is also blocking #220
The text was updated successfully, but these errors were encountered: