Closed tony closed 7 years ago
Can we just make next realease with support of Django versions which is officially supported right now?
Which could be 1.8+, and python 2.7+
Yep.
Can You push AUTHORS and add all https://github.com/hellysmile/django-activeurl/graphs/contributors this guys?
According to https://www.djangoproject.com/download/ we need to leave 1.8, 1.10 and 1.11 As well it will be great to start testing 2.0, maybe just django master branch?
Good point, we can opt out of 1.9.
And yeah nothing wrong with adding travis/tox tests to master.
We can drop frosted linter as well, this lib is dead.
Another great step forward can be replace nose by pytest
Right now here is copy of test matrix from tox to travis, which can be omitted - here is an example how we do it https://github.com/wikibusiness/aioelasticsearch
Fine with me (re: tox -> travis)
Here is what django-extensions does: tox.ini .travis.yml
Also, love pytest.
Fixed #29
@hellysmile next thing, let's get CI greenlighting
What do you want to have happen re: old django, 1.7 and less. Keep or let them go?
patterns()
deprecated in 1.8), that's fixed via newer django versions too