Should we remove Django 1.8 support and create a minor version? I was planning to create this version after the Redesign Issue but it can also be a major version bump.
Any opinions @erkanay, @gonulsabah, @aymankh86 and other people who uses this module? Is anybody out there using nece on Django 1.8 or is it just us? 😱
How about creating 0.6.x version and drop 1.8 support and keep 0.5.x branch with 1.8 support and keep developing both versions until completely removing compatibility?
We support Django 1.8 in a very hacky way which leads us to add some silly workarounds throughout the code base.
Please see @kemar's pull-request
Should we remove Django 1.8 support and create a minor version? I was planning to create this version after the Redesign Issue but it can also be a major version bump.
Any opinions @erkanay, @gonulsabah, @aymankh86 and other people who uses this module? Is anybody out there using
nece
on Django 1.8 or is it just us? 😱