Next release - 1.1.9 and 1.2.0

[deniszh]

Sorry for not releasing 1.1.9 as I promised - too many things happened recently around me. 1.1.9 is almost done, I only need to write release notes and release it. But probably it would be better to release 1.2.0 also soon. I mean it's clearly visible that supporting Python 2.7 and old versions of Django becoming harder and harder. So, I'm proposing following plan:

1. Release 1.1.9 would be done soon, as usual, tagging release in 1.1.x branch, as is.
2. After that we should prepare 1.2.0 release from master, with

• officially dropping support of old Python (2.7 and 3.6 and earlier). Not actively cleaning up code yet, but officially declare that, at least.
• officially dropping support of old Django (after April 2022 single supported Django version is 3.2 TLS, supporting new Python only)
• officially dropping support of old versions of other modules if needed. Totally possible, that would cause some side effects, e.g. we probably should drop support of django-tagging, potentially dropping support of Events API. Migration to taggit is possible, but migration of data model although potentially possible but could be hard.

3. All follow up releases would be done from master branch, with possible backports to 1.1.x if needed (which should be much better, current backport process from master is PITA).

That should improve release process and open way to modernize codebase.

[brd]

ping? I would like to bring graphite back to FreeBSD ports/packages but need support for an active version of django.

[deniszh]

Hi Brad, Yes, thanks for ping, still on my plate.