Updated plan, with more info about deployment under Python 3 and reordered priorities.
- Legacy-Id: 16640
This commit is contained in:
parent
92590b70bf
commit
0a7060316c
12
PLAN
12
PLAN
|
@ -7,11 +7,6 @@ Updated: $Date$
|
|||
Planned work in rough order
|
||||
===========================
|
||||
|
||||
* Complete the transition to Python 3. This will make it easier to add add
|
||||
support for internationalsed email, and also other i18n enhancements. The
|
||||
code has now been made Python 2 / Python 3 compatible (as of release 6.99.0,
|
||||
16 July 2019), but has not been deployed under Python 3 yet.
|
||||
|
||||
* Change the draft submission form so that an email address is required for
|
||||
each author in order to complete self-service draft submission. Missing
|
||||
email address(es) will lead to failure, and require submission via the
|
||||
|
@ -29,6 +24,13 @@ Planned work in rough order
|
|||
|
||||
* Revisit the review tool, work through the accumulated tickets.
|
||||
|
||||
* Complete the transition to Python 3. This will make it easier to add add
|
||||
support for internationalsed email, and also other i18n enhancements. The
|
||||
code has now been made Python 2 / Python 3 compatible (as of release 6.99.0,
|
||||
16 July 2019), but has not been deployed under Python 3 yet. The natural
|
||||
point for changing the deployment seems to be just after the next OS upgrade,
|
||||
which we think will make Python 3.6 the default mod_wsgi python.
|
||||
|
||||
* Review and change the draft submission and handling code to deal with UTF-8
|
||||
instead of ascii before upload of utf-8 drafts should be permitted.
|
||||
(This may fall out for free with the Python 3 transition).
|
||||
|
|
Loading…
Reference in a new issue