[tor-commits] [trunnel/master] Add more todo items based on an email I sent; bump version to 1.4-pre

[nickm at torproject.org]

commit 599017a1bf98fe824691509ee6df9f4922460054
Author: Nick Mathewson <nickm at torproject.org>
Date:   Wed Oct 8 15:37:17 2014 -0400

    Add more todo items based on an email I sent; bump version to 1.4-pre
---
 TODO                    |   23 ++++++++++++++++++++++-
 lib/trunnel/__init__.py |    2 +-
 2 files changed, 23 insertions(+), 2 deletions(-)

diff --git a/TODO b/TODO
index 243f991..371845c 100644
--- a/TODO
+++ b/TODO
@@ -7,7 +7,7 @@ FOR VERSION 1
 
   o Windows support (msvc, mingw)
 
-FOR VERSION 1.1 OR LATER
+FOR VERSION 2 OR LATER
 
   - Correctness:
     - Allow union case statements to contain ranges that involve named
@@ -26,4 +26,25 @@ FOR VERSION 1.1 OR LATER
   - Code quality:
     - Simplify huge union case statements.
 
+MORE IDEAS FOR PEOPLE WHO WOULD LIKE TO HACK ON TRUNNEL
+
+  * It would be cool to have a formal specification of trunnel's input
+language, and maybe even a proof of some parts of trunnel's
+correctness.
+
+  * The code is not as clean as it could be, in spite of its level of
+coverage.  It would be good to identity refactoring opportunities.
+
+  * There are probably more tests we could do.
+
+  * It might be interesting to provide a mechanism to plug in external
+data types and transformations.
+
+  * If you use Trunnel for a while yourself, you will probably find
+other things that should be improved in it.  (This might be the best
+way to proceed: use-motivated changes are probably much smarter than
+theory-motivated ones.)
+
+  * It might be interesting to write something that can take trunnel
+grammars and output a fuzzer for alleged parsers of those formats.
 
diff --git a/lib/trunnel/__init__.py b/lib/trunnel/__init__.py
index 8dcc7ff..b39d47a 100644
--- a/lib/trunnel/__init__.py
+++ b/lib/trunnel/__init__.py
@@ -3,4 +3,4 @@
 # a package.
 #
 
-__version__ = "1.3"
+__version__ = "1.4-pre"