Reduce testing time in travis

[Radi85]

Change Type

[ ] Refactor/Enhancement
[ ] Testing
[x] CI/CD
[ ] Other

Proposed Changes

Reduce the testing time in travis by reducing the number of python and django compatibility versions.
We can use the most first and most recent version that our app is compatible with.

For python:

• 3.6
• 3.8

django:

• 2.1
• 3.1
• django-master

[abhiabhi94]

for documentation specific changes, you may use the [skip ci] in commit message to allow it to pass. This link suggests another option.

Regarding the testing time on travis, someone it does takes a lot of time but this is usually not due to us but something because of them. The tests not take more than 10min to run on all supported versions as of now. I had an email from them that they are going to transfer all repositories to travis-ci.com and the org version will be dead by the end of this year. Maybe that could be a reason.

[abhiabhi94]

Also, the issue template formatting needs to be updated, I have edited the comment on this one, but it needs to be done in the codebase to be fixed for future.

[Radi85]

for documentation specific changes, you may use the [skip ci] in commit message to allow it to pass. This link suggests another option.

Regarding the testing time on travis, someone it does takes a lot of time but this is usually not due to us but something because of them. The tests not take more than 10min to run on all supported versions as of now. I had an email from them that they are going to transfer all repositories to travis-ci.com and the org version will be dead by the end of this year. Maybe that could be a reason.

Thanks for the info.
In fact why do we need to check the compatibility for every version? What I have mentioned above is enough to cover the versions in between.

[Radi85]

Also, the issue template formatting needs to be updated, I have edited the comment on this one, but it needs to be done in the codebase to be fixed for future.

What needs to be updated?

[abhiabhi94]

What needs to be updated?

you have changed my edit. my version would reflect the to-do list as:

• Refactor/Enhancement
• Testing
• CI/CD
• Other

while as of now, you can see the to-do list is not rendered correctly.

[Radi85]

What needs to be updated?

you have changed my edit. my version would reflect the to-do list as:

• Refactor/Enhancement
• Testing
• CI/CD
• Other

while as of now, you can see the to-do list is not rendered correctly.

😄 I have updated it already.

[abhiabhi94]

Radico's TODO

Abhyudai's TODO

[Radi85]

Ahhh 😄 , in face this is not a TODO list but just an option of the change type. TODO means that all items should be implemented and this is not the case in issue templates.
Also I list the choices similarly to Github's auto generated issue templates.