From 1b644cbb5c8f9b64323dc7ead5841dcc5e195d6f Mon Sep 17 00:00:00 2001 From: Garret Wassermann Date: Tue, 3 Jul 2018 00:51:27 -0400 Subject: [PATCH] Updated Development Roadmap (markdown) --- Development-Roadmap.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Development-Roadmap.md b/Development-Roadmap.md index 956f8c0..fe7798a 100644 --- a/Development-Roadmap.md +++ b/Development-Roadmap.md @@ -5,14 +5,14 @@ This is very much in flux, nothing set in stone yet, just ideas looking for comm # Upcoming Releases ## 0.3 -* Require Django 1.11.x or 2.x, Python 3.4+ +* Require Django 2.x, Python 3.4+ * Revisit Django deprecation warnings, fully address all deprecated issues from 1.8 -> 1.11 LTS transition; according to the Django deprecation guide, allows code to run until after the next LTS, so 1.11 code works on 2.x too, but would require further porting for 3.x, etc.) * Message threading, revised UI (should we use CoreUI? http://coreui.io) * Merged tickets and improved bulk actions * Improved Django user permissions ## 0.4 -* Require Django 2.x, Python 3.5+, (Python 2 is dropped for sure) +* Require Django 2.x, Python 3.5+ * Port from Django 1.11.x -> 2.x to address deprecated features in 1.11 series * Generic views? (Should re-evaluate best practices when Django 2.0 is released, Django itself may change a bit in major version) @@ -36,6 +36,7 @@ This is very much in flux, nothing set in stone yet, just ideas looking for comm * 0.2.3 - get_mail fixes, zh_Hans translation - 2017-12-09 * 0.2.4 - 2017-12-18 * 0.2.6 - 2017-12-28 - collectstatic bugfix and Django 2.0 compatibility (mostly) +* 0.2.8 - 2018-07-03 - more bugfixes to work with Django 2.x / Python 3.x ## 0.1.18 - last update end of 2016 * The classic release, we released 0.1.18 to fix a few bugs and simple merge requests.