[Zope-Checkins] CVS: Zope - TODO.txt:1.1.2.14

[Fred L. Drake, Jr.]

Update of /cvs-repository/Zope
In directory cvs.zope.org:/tmp/cvs-serv22137

Modified Files:
      Tag: chrism-install-branch
	TODO.txt 
Log Message:
- move a couple of items to done
- add comments/questions on several items


=== Zope/TODO.txt 1.1.2.13 => 1.1.2.14 ===
--- Zope/TODO.txt:1.1.2.13	Fri Jan 24 11:27:52 2003
+++ Zope/TODO.txt	Fri Jan 24 11:47:25 2003
@@ -80,11 +80,6 @@
   This change needs to be communicated in docs and to developers in
   some way.
 
-No easy way to specify to log to stdout
-
-  Need another log handler type in the Zope schema (consolehandler?)
-  to specify a stdout log.
-
 "configure" shell scripts need peer review
 
   I'd like someone to review the "configure" and "configure.bat"
@@ -119,18 +114,6 @@
   "overrides" or "getSchemaKeys" is likely aiming to deal with this),
   but none of it actually works.
 
-Normalize zLOG/PEP 282 logging severities
-
-  Currently there is an unintuitive mapping between zLOG and PEP 282
-  (logging package) severities.  The config file allows you to specify
-  log severities using the PEP282 semantics, but you need to dig into
-  the source code to find out what the mappings are between zLOG
-  severities and PEP 282 severities (inside zLOG.EventLogger).  Find
-  some way to make this make sense either via documentation or by
-  extending the PEP282 logger with zLOG severities and changing the
-  schema to allow the specification of zLOG severities instead of
-  PEP282 severities.
-
 Find a place for zLOG.DebugLogger and zLOG.AccessLogger
 
   These packages are placed here because I've got no better place for
@@ -200,6 +183,10 @@
   directory.  Alternately the RPM install should not contain .pycs or
   .pyos.
 
+  XXX Not clear why this is actually needed; importing a module causes
+  the __file__ to be updated with the right filename.  A nice touch,
+  but not required.
+
 RPM install versioning scheme needs to be documented
 
   The RPM builder has a versioning scheme via the generated Makefile
@@ -263,6 +250,10 @@
   a config file are FileStorage and ClientStorage.  We need to include
   the rest of them.
 
+  XXX We expect this will be picked up on merging to the trunk, where
+  the ZODB schema component provides support for all "stock" storage
+  types.
+
 Normalize Zope schema segments for logging and database against ZEO schema
 
   Once ZEO configuration has a ZConfig schema, make sure to sanity
@@ -271,6 +262,10 @@
   to schema support which allow you to import a schema fragment for
   use in multiple different schemas.
 
+  XXX We will use the schema components provided by zLOG and ZODB.
+  zLOG with schema support has already been merged into the branch;
+  still need to integrate.  Waiting on testing.
+
 Test 'effective user' support
 
   Great pains have been taken in configuration integration to defer
@@ -284,8 +279,7 @@
   The branch takes the strategy of logging to stdout and buffering log
   messages until "real" loggers can safely be configured.  After
   "real" loggers are configured, the log messages buffered at startup
-  are flushed to the "real" loggers.  Ensure this meets everybody's
-  satisfaction via zope-coders (or don't, it's a rathole).
+  are flushed to the "real" loggers.
 
 Server construction errors need to be better
 
@@ -316,6 +310,8 @@
   When Zope starts, it's been asserted in various maillist threads
   that it should chdir to '/'.  This is not done.
 
+  XXX Why should it be done?
+
 Performing the merge
 
   I am not at all confident that doing a cvs up -j
@@ -397,6 +393,29 @@
 
 DONE
 ----
+
+Normalize zLOG/PEP 282 logging severities
+
+  Currently there is an unintuitive mapping between zLOG and PEP 282
+  (logging package) severities.  The config file allows you to specify
+  log severities using the PEP282 semantics, but you need to dig into
+  the source code to find out what the mappings are between zLOG
+  severities and PEP 282 severities (inside zLOG.EventLogger).  Find
+  some way to make this make sense either via documentation or by
+  extending the PEP282 logger with zLOG severities and changing the
+  schema to allow the specification of zLOG severities instead of
+  PEP282 severities.
+
+  Done by Guido in zLOG, 23 Jan 2003.
+
+No easy way to specify to log to stdout
+
+  Need another log handler type in the Zope schema (consolehandler?)
+  to specify a stdout log.
+
+  Done 23 Jan 2003; the new zLOG support allows a <filehandler> to
+  specify a path of STDOUT or STDERR, causing output to go to the
+  named stream.
 
 "zctl.py" program needs to be renamed to "zopectl.py"