<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.3.2">
</HEAD>
<BODY>
Well, Ian and I are both exhausted (metaphorically.)<BR>
<BR>
It is a rare project that does not release with known bugs.<BR>
<BR>
But 0.6.0.rc1 can serve as well as 0.6.0 for most people, so <BR>
I don't mind using that name --- but I will make a tar file of it,<BR>
for the convenience of a hypothetic new user. If they choose <BR>
not to use class-indexing, they will not experience the known<BR>
bugs; it is the unknown once that will be the problem.<BR>
<BR>
But we do have a solid test suite, relatively speaking.<BR>
<BR>
On Wed, 2006-02-22 at 23:01 -0500, Waldo Rubinstein wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
<FONT COLOR="#000000">How about releasing 0.6.0.rc1 instead? It just doesn't fly well with me the fact that a new release is coming out with known bugs. I understand your point. The question is, like Ian asked, is it worth fixing this bug or re-engineering to closer-to-mop.</FONT><BR>
<BR>
<BR>
<FONT COLOR="#000000">- Waldo</FONT><BR>
<BR>
<FONT COLOR="#000000">On Feb 22, 2006, at 10:43 PM, Robert L. Read wrote:</FONT><BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<FONT COLOR="#000000">Thanks for this large and excellent body of work, Ian.</FONT><BR>
<BR>
<FONT COLOR="#000000">I agree that we should use closer-to-mop.</FONT><BR>
<BR>
<FONT COLOR="#000000">However, I am tempted to release 0.6.0 even in the presence of these bugs, </FONT><BR>
<FONT COLOR="#000000">as all of them concern the new functionality that you have added. I am pretty</FONT><BR>
<FONT COLOR="#000000">confident 0.6.0 represents no regression from previous releases, and certainly</FONT><BR>
<FONT COLOR="#000000">is better in other ways.</FONT><BR>
<BR>
<FONT COLOR="#000000">On Wed, 2006-02-22 at 17:28 -0500, Ian Eslick wrote: </FONT>
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">These do not appear to be properly implemented for persistent slots on</FONT>
<FONT COLOR="#000000">any platform. This may be part of the problem that Andrew, Robert and I</FONT>
<FONT COLOR="#000000">are looking at. It should be easy to add, but I don't understand why</FONT>
<FONT COLOR="#000000">it's not failing.</FONT>
<FONT COLOR="#000000">I also found a couple of small problems I introduced into the tests</FONT>
<FONT COLOR="#000000">accidentally while exploring these bugs. I have fixed these in my</FONT>
<FONT COLOR="#000000">latest checkin. If you're working on these bugs, please update:</FONT>
<FONT COLOR="#000000">My full status as of this checkin is:</FONT>
<FONT COLOR="#000000">Mac OS X 10.4 / ACL 8.0 / BDB -</FONT>
<FONT COLOR="#000000"> Backend: Green </FONT>
<FONT COLOR="#000000"> Migration: Green</FONT>
<FONT COLOR="#000000">Mac OS X 10.4 / ACL 8.0 / SQL -</FONT>
<FONT COLOR="#000000"> Backend:</FONT>
<FONT COLOR="#000000"> Fails: INDEXING-CHANGE-CLASS (fails due to get-instances-by-value</FONT>
<FONT COLOR="#000000">returning 0 instead of 1 instance)</FONT>
<FONT COLOR="#000000"> Fails: INDEXING-REDEF-CLASS (fails due to get-instances-by-value</FONT>
<FONT COLOR="#000000">returns 2 instead of 1 instance)</FONT>
<FONT COLOR="#000000"> Migration:</FONT>
<FONT COLOR="#000000"> Fails: MIGRATE-IPCLASS (fails due to get-instances-by-value</FONT>
<FONT COLOR="#000000">returning 2 instead of 1)</FONT>
<FONT COLOR="#000000">Mac OS X 10.4 / SBCL 8.0 / BDB</FONT>
<FONT COLOR="#000000"> Backend:</FONT>
<FONT COLOR="#000000"> Fails: INDEXING-REDEF-CLASS (slot not found bug discussed in earlier</FONT>
<FONT COLOR="#000000">e-mail)</FONT>
<FONT COLOR="#000000"> Migration: Green</FONT>
<FONT COLOR="#000000">Mac OS X 10.4 / SBCL 8.0 / SQL</FONT>
<FONT COLOR="#000000"> Backend:</FONT>
<FONT COLOR="#000000"> Fails: INDEXING-REDEF-CLASS (slot not found bug discussed in earlier</FONT>
<FONT COLOR="#000000">e-mail)</FONT>
<FONT COLOR="#000000"> Migration:</FONT>
<FONT COLOR="#000000"> Fails: MIGRATE-IPCLASS (fails due to get-instances-by-value</FONT>
<FONT COLOR="#000000">returning 2 instead of 1)</FONT>
<FONT COLOR="#000000">I'm beginning to think that porting over to a MOP compatibility layer</FONT>
<FONT COLOR="#000000">(like closer-to-mop) may be a better course than to continue to patch</FONT>
<FONT COLOR="#000000">the current system if no one can find this with a little more effort. I</FONT>
<FONT COLOR="#000000">don't have time for at least two weeks to look at this. I will be</FONT>
<FONT COLOR="#000000">available to answer questions, but not for any significant debugging or</FONT>
<FONT COLOR="#000000">development.</FONT>
<FONT COLOR="#000000">Ian</FONT>
<FONT COLOR="#000000">_______________________________________________</FONT>
<FONT COLOR="#000000">elephant-devel site list</FONT>
<FONT COLOR="#000000"><A HREF="mailto:elephant-devel@common-lisp.net">elephant-devel@common-lisp.net</A></FONT>
<FONT COLOR="#000000"><A HREF="http://common-lisp.net/mailman/listinfo/elephant-devel">http://common-lisp.net/mailman/listinfo/elephant-devel</A></FONT>
</PRE>
</BLOCKQUOTE>
<FONT COLOR="#000000">_______________________________________________</FONT><BR>
<FONT COLOR="#000000">elephant-devel site list</FONT><BR>
<FONT COLOR="#000000"><A HREF="mailto:elephant-devel@common-lisp.net">elephant-devel@common-lisp.net</A></FONT><BR>
<FONT COLOR="#000000"><A HREF="http://common-lisp.net/mailman/listinfo/elephant-devel">http://common-lisp.net/mailman/listinfo/elephant-devel</A></FONT><BR>
</BLOCKQUOTE>
<BR>
<BR>
<PRE>
<FONT COLOR="#000000">_______________________________________________</FONT>
<FONT COLOR="#000000">elephant-devel site list</FONT>
<FONT COLOR="#000000"><A HREF="mailto:elephant-devel@common-lisp.net">elephant-devel@common-lisp.net</A></FONT>
<FONT COLOR="#000000"><A HREF="http://common-lisp.net/mailman/listinfo/elephant-devel">http://common-lisp.net/mailman/listinfo/elephant-devel</A></FONT>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>