These are chat archives for jcassee/django-analytical

6th
Jan 2016
Joost Cassee
@jcassee
Jan 06 2016 14:44
@bittner Do you think we can release master as 1.1.0 or should we call it 2.0.0? It does break some compatibility, but it's for Django versions that are not supported anymore anyway. (I lean towards 1.1.0.)
Peter Bittner
@bittner
Jan 06 2016 16:15
What compatibility does it break, specifically? Version 1.1.0 sounds good to me.
@jcassee Can you activate GitHub integration in the side panel on the right? (Gitter) -- We may get a list of the latest commits then.
Joost Cassee
@jcassee
Jan 06 2016 19:35
Well, it breaks compatibility with Django < 1.7 and Python < 2.7?
Ehm, I don't see anything to do with integration in the right hand side panel? The settings menu seems to suggest that GitHub is already integrated...
Peter Bittner
@bittner
Jan 06 2016 22:07
There's probably something wrong with the webhooks. It could be the permissions for 3rd party apps, GitHub restricted that a while ago. Can you check if you need to give permissions to Gitter? (disconnect + reconnect)
Sure, that's in fact a big change, dropping support completely for some versions. :grimacing:
Peter Bittner
@bittner
Jan 06 2016 22:36
I'm wondering what we really changed that breaks backward-compatibility. Isn't it all about the tests, really? The app as such may run (though we can't prove it any more via our tests).
Peter Bittner
@bittner
Jan 06 2016 22:46
No, really, let's do a "2.0" version. It's more honest this way. Also, 1.0 and below would be the versions that supported a huge range of Django releases. That's worth a page of its own in a history book. Now this time is over.