[Checkins] SVN: z3c.autoinclude/tags/0.3/ finalize 0.3 release

[Ethan Jucovy]

Log message for revision 97468:
  finalize 0.3 release

Changed:
  U   z3c.autoinclude/tags/0.3/CHANGES.txt
  U   z3c.autoinclude/tags/0.3/TODO.txt
  U   z3c.autoinclude/tags/0.3/setup.py

-=-
Modified: z3c.autoinclude/tags/0.3/CHANGES.txt
===================================================================
--- z3c.autoinclude/tags/0.3/CHANGES.txt	2009-03-04 02:40:58 UTC (rev 97467)
+++ z3c.autoinclude/tags/0.3/CHANGES.txt	2009-03-04 02:41:23 UTC (rev 97468)
@@ -1,8 +1,8 @@
 Changes
 =======
 
-0.3 (unreleased)
-------------------
+0.3 (2009-03-03)
+----------------
 
 * Allow virtual namespace packages like 'plone' to be specified for the package. I think this
   may need more thought for the dependency case.

Modified: z3c.autoinclude/tags/0.3/TODO.txt
===================================================================
--- z3c.autoinclude/tags/0.3/TODO.txt	2009-03-04 02:40:58 UTC (rev 97467)
+++ z3c.autoinclude/tags/0.3/TODO.txt	2009-03-04 02:41:23 UTC (rev 97468)
@@ -1,8 +1,14 @@
 in no particular order, some notes on things that I think ought to happen to this code:
 
  * Profiling.  As far as I know, none has been done, and I expect that the code is *very* slow. Then, obviously, optimizations should be considered.
- * Documentation.  It's still fairly poor; I think the whole damn thing is just so abstract that I can't figure out how to talk about it.
- * May as well figure out how to make a PasteScript template to auto-generate the entry point.
- * Better debugging tools/APIs: to see what will be autoincluded, turn on and off autoinclusion for individual packages, and freeze a ZCML file capturing autoinclusion information a la pip.
+   See also http://mail.zope.org/pipermail/zope-dev/2009-February/034866.html
+ * Documentation.  I'm trying to keep user and developer documentation both up-to-date and helpful, but I'm not sure I'm doing a very good job of
+   keeping it helpful.  Please let me know what's missing or unclear.
+ * I want to figure out how to make a PasteScript template to auto-generate the entry point for a plugin package, but I never seem to find the time
+   to learn how to write PasteScript templates.
+ * Better debugging tools/APIs are one of my highest priorities for this package in the short and long term.  I'd like to make it very easy to see
+   what will be autoincluded, turn on and off autoinclusion for individual packages, and freeze a ZCML file to capture static autoinclusion information
+   (a la pip).
 
-One day I also want to add another directive to autoinclude subpackages' ZCML; this is a frequent annoyance for me (see https://svn.openplans.org/svn/opencore/trunk/opencore/configuration/configure.zcml for an illustrative example)
+One day I also want to add another directive(s) to autoinclude subpackages' ZCML; this is a frequent annoyance for me (see
+https://svn.openplans.org/svn/opencore/trunk/opencore/configuration/configure.zcml for an illustrative example)

Modified: z3c.autoinclude/tags/0.3/setup.py
===================================================================
--- z3c.autoinclude/tags/0.3/setup.py	2009-03-04 02:40:58 UTC (rev 97467)
+++ z3c.autoinclude/tags/0.3/setup.py	2009-03-04 02:41:23 UTC (rev 97468)
@@ -5,7 +5,7 @@
                     open('CHANGES.txt').read())
 
 setup(name='z3c.autoinclude',
-      version='0.3dev',
+      version='0.3',
       description="Automatically include ZCML",
       long_description=long_description,
       # Get more strings from http://www.python.org/pypi?%3Aaction=list_classifiers