Updated Development Roadmap (markdown)

Garret Wassermann 2017-08-29 18:00:28 -04:00
parent 6090360bde
commit 0ff518a44d

@ -1,6 +1,7 @@
Below is a roadmap and rough timeline for major new features and changes to django-helpdesk.
This is very much in flux, not set in stone yet, and looking for comments! Please feel free to file a ticket if you'd like to discuss an idea, or directly add ideas to this wiki.
This is very much in flux, nothing set in stone yet, just ideas looking for comments! Please feel free to file a ticket if you'd like to discuss an idea, or directly add ideas to this wiki.
# Upcoming Releases
## 0.2
@ -12,18 +13,24 @@ This is very much in flux, not set in stone yet, and looking for comments! Pleas
## 0.3
* Require Django 1.11+, Python 2.7 or 3.4+, last release to support Python 2.7
* Message threading, revised UI
* Merged tickets and improved bulk actions
* Improved Django user permissions
## 0.4
* Require Django 2.0+, Python 3.5+
* Generic views? (Should re-evaluate best practices as Django 2.0 gets closer, Django itself may change a bit in major version)
## Future (Not yet scheduled)
* Public-facing web interface overhaul, rework how we allow ticket submitters to log in and view status without accounts
* API using django-rest-framework or similar (internal django-helpdesk API was deprecated in 0.1.18, removed in 0.2)
* Move to Bootstrap CSS v4.0 once released
* Move to Font Awesome 5 Free once released
# Past Releases
## 0.1 - last update end of 2016
## 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.
* Expect 0.1.18 to be the last release of the series as we move to further development.
* Supports south databases and Django prior to 1.8, both python 2.7 and 3.3+
* Supports south databases and Django prior to 1.8
* Requires Python 2.7+, some features supported on 3.3+ (but not totally official, particularly email submission of tickets)