[elephant-cvs] CVS elephant

[ieslick]

Update of /project/elephant/cvsroot/elephant
In directory clnet:/tmp/cvs-serv29707

Modified Files:
	TODO 
Log Message:
Exploring SBCL failures & incorporating Andrew Blumberg's SBCL MOP fix

--- /project/elephant/cvsroot/elephant/TODO	2006/02/22 22:01:44	1.18
+++ /project/elephant/cvsroot/elephant/TODO	2006/02/25 17:04:56	1.19
@@ -1,16 +1,15 @@
-Written support
-Poster - vision + concrete value
 
-Feb 6, 2006
+Feb 23, 2006
 
 Release plan in-discussion with Robert and Ian
 
-Upcoming release ideas.
-
-0.6.0 - Adding default class/slot indexing
-- Resolve stubbed out slot-boundp bug in indexing-reconnect-db test (Ian)
-- Finish CLSQL backend debug (Robert)
-- Documentation update (Robert)
+0.6.0 - Adding default class/slot indexing; modularize backends
+Bugs (0 failures of test suite):
+- Resolve stubbed out slot-boundp/MOP bug in indexing-reconnect-db test under SBCL
+- Resolve SQL range query bug
+Tasks:
+- Documentation update
+- Tutorial review 
 
 0.6.1 - performance, safety and portability
 
@@ -19,7 +18,6 @@
 - Verify that operations such as indexing are thread safe
 
 Stability
----------
 - Review all the NOTE comments in the code
 - Remove build gensym warnings in sleepycat
 - Port elephant to closer-to-MOP to make it easier to support additional lisps (Both)
@@ -64,9 +62,6 @@
   index without any secondary indices or indexed slots (Ian)
 - Add :inverse-reader to slot options to create a named method that indexes into objects 
   based on slot values.  Is this a GF or defun?  Do we dispatch on class name or bake it in?
-- On class change, new slots should have their initform values pushed 
-  into the slot value as if the slot was being created the first time 
-  (currently this doesn't happen) (Ian)
 
 Bugs:
 - anything else reported against 0.5.0/0.6.0
@@ -112,6 +107,11 @@
   - A native BTree implementation in CommonLisp (prototype on Allegro's BTree implementation for ACache)
 
 
+Resolved issues:
+- On class change, new slots should have their initform values pushed 
+  into the slot value as if the slot was being created the first time 
+  (currently this doesn't happen) [fixed in 0.6.0-rc1]
+
 Feb. 4, 2006
 
 As of 0.5.0, we have seem to have a stable suite on