move very old dev notes down a level

Author: minrk

docs/source/index.rst

@@ -58,17 +58,9 @@ You can also check out the `examples in the pyzmq repo <https://github.com/zerom
     eventloop.rst
     logging.rst
     ssh.rst
+    notes/index.rst
 
 
-Notes from developing PyZMQ
-===========================
-
-.. toctree::
-    :maxdepth: 2
-
-    pyversions.rst
-    unicode.rst
-
 Indices and tables
 ==================
 

docs/source/notes/index.rst

@@ -0,0 +1,11 @@
+Notes from developing PyZMQ
+===========================
+
+These are old notes from the early days of developing pyzmq,
+back when we needed to support Python 2.5 and 3.1.
+
+.. toctree::
+    :maxdepth: 1
+
+    pyversions.rst
+    unicode.rst

docs/source/pyversions.rst renamed to docs/source/notes/pyversions.rst

@@ -1,10 +1,14 @@
-.. PyZMQ Version compatibility doc, by Min Ragan-Kelley, 2010
-
 .. _pyversions:
 
 PyZMQ, Python2.5, and Python3
 =============================
 
+.. note::
+
+    This describes early days of pyzmq development,
+    when we supported Python 2.5 and 3.1.
+    Much of this information is wildly outdated now.
+
 PyZMQ is a fairly light, low-level library, so supporting as many versions
 as is reasonable is our goal.  Currently, we support at least Python 2.5-3.1.
 Making the changes to the codebase required a few tricks, which are documented here

docs/source/unicode.rst renamed to docs/source/notes/unicode.rst

@@ -1,10 +1,14 @@
-.. PyZMQ Unicode doc, by Min Ragan-Kelley, 2010
-
 .. _unicode:
 
 PyZMQ and Unicode
 =================
 
+.. note::
+
+    This describes early days of pyzmq development,
+    when we supported Python 2.5 and 3.1.
+    Much of this information is wildly outdated now.
+
 PyZMQ is built with an eye towards an easy transition to Python 3, and part of
 that is dealing with unicode strings. This is an overview of some of what we
 found, and what it means for PyZMQ.