[Zope3-checkins] CVS: Zope3/doc - TODO.txt:1.67 TODOLATER.txt:1.12

Stephan Richter srichter at cosmos.phy.tufts.edu
Wed Apr 28 13:54:43 EDT 2004


Update of /cvs-repository/Zope3/doc
In directory cvs.zope.org:/tmp/cvs-serv27575/doc

Modified Files:
	TODO.txt TODOLATER.txt 
Log Message:
Removed some TODO items. It is better to meet the deadlines at this point.


=== Zope3/doc/TODO.txt 1.66 => 1.67 ===
--- Zope3/doc/TODO.txt:1.66	Tue Apr 27 13:24:53 2004
+++ Zope3/doc/TODO.txt	Wed Apr 28 13:54:41 2004
@@ -1,11 +1,10 @@
 ============================================================
-Things to do for the next release (in no particular order)
+Things to do for the next release (sorted by importance)
 ============================================================
 
-- Persistent interfaces cannot be provided as providedBy or implementedBy
-  interfaces anymore. This functionality was broken during some interface and
-  adapter refactorings. Originally this was out of scope, but I think it is
-  too important and fundamental to be left out.
+- Distribution, packaging an installation system.  Fred is working on
+  a prototype. This will eventually inclide Zope-2 style installation,
+  configuration and process management.
 
 - http://dev.zope.org/Zope3/NoMoreSchemaBinding
 
@@ -16,12 +15,6 @@
   This is needed for a number of other tasks.  Nathan Yergler is
   working on this.
 
-- Merge zope.conf and zdaemon.conf. This is a Fred Drake task. :)
-
-- Distribution, packaging an installation system.  Fred is working on
-  a prototype. This will eventually inclide Zope-2 style installation,
-  configuration and process management.
-
 - Redo event service
 
   o Simplify publication/registration framework
@@ -34,36 +27,22 @@
 
   http://dev.zope.org/Zope3/FixedDefaultComponentLookup
 
-- Partial adapters
-
-  http://dev.zope.org/Zope3/PartialAdapters
-
-  Maybe we can live without these.
-
-- Minor refactoring of security context
-
-  http://dev.zope.org/Zope3/UnificationOfRequestsAndSecurityContextsThroughUse
-
-  Steve and Marius are working on this
-
-- Restructure registration framework to use direct references rather
-  than paths.
-
 - Finish location-relevent event work;
   specifically, handling events on containers.  
 
-  See:
-   http://dev.zope.org/Zope3/LocationRelatedEvents
+  See: http://dev.zope.org/Zope3/LocationRelatedEvents
 
 - Redo the way names input in add forms.
 
   See: http://dev.zope.org/Zope3/AddingNameControl
 
-  K. Narasimha Murthy is working on this.
+- Minor refactoring of security context
 
-- http://dev.zope.org/Zope3/LifeCycleEvents
+  http://dev.zope.org/Zope3/UnificationOfRequestsAndSecurityContextsThroughUse
 
-- Permission rationalization
+  Steve and Marius are working on this
 
-  Absent deep thinking, then create a set of fine-grained permission
-  and a default permission redefinition that makes them course grained
+- Persistent interfaces cannot be provided as providedBy or implementedBy
+  interfaces anymore. This functionality was broken during some interface and
+  adapter refactorings. Originally this was out of scope, but I think it is
+  too important and fundamental to be left out.


=== Zope3/doc/TODOLATER.txt 1.11 => 1.12 ===
--- Zope3/doc/TODOLATER.txt:1.11	Tue Apr 27 13:24:53 2004
+++ Zope3/doc/TODOLATER.txt	Wed Apr 28 13:54:41 2004
@@ -2,6 +2,24 @@
 Things to do After the next release (in no particular order) 
 ============================================================
 
+- Restructure registration framework to use direct references rather
+  than paths.
+
+- Partial adapters
+
+  http://dev.zope.org/Zope3/PartialAdapters
+
+  Maybe we can live without these.
+
+- Merge zope.conf and zdaemon.conf. This is a Fred Drake task. :)
+
+- http://dev.zope.org/Zope3/LifeCycleEvents
+
+- Permission rationalization
+
+  Absent deep thinking, then create a set of fine-grained permission
+  and a default permission redefinition that makes them course grained
+
 - Implement graceful shutdown and restart a la Zope 2. We have to add a bit of
   code to the server to support this, but it should not be too hard, since we
   have an implamentation in Zope 2.




More information about the Zope3-Checkins mailing list