Scribit Robert L. Read dies 03/04/2007 hora 11:30: > I'm pleased that you think Elephant is ready for a 1.0 release, but > unfortunately Ian and I disagree. Ian and I have a number of small > features that we think are needed to be "1.0 complete", not lease of > which is an off-line garbage collection, and the integration of the > "postmodern" backend.
Well, on the other hand, I think making something 1.0 won't make it vastly more popular or widely used. So maybe we could just continue the conservative way: continue under 1.0, that is, 0.7, 0.8, 0.9, 0.10 and so on, until we get at least: - confidence that there can't be data loss when using it, - two or three big systems deployed for some months with some reasonable load Because there's something sure: labeling 1.0 a package that can make the application based on it break or lose data is really dangerous, in terms of image. So there's nothing to lose in waiting, but much if we go too fast. I would also prefer to label 1.0 an release of Elephant that is certain to work pretty everywhere, that is on all major CL implementations and maybe even one or two exotic ones. That probably means using portability layers for things lile MOP and threads. I'm willing to help, or even take full responsibility for porting Elephant to Closer-MOP and Bordeaux Threads. As UFFI has gone unmaintained, I'd also suggest moving to CFFI, which, IIRC, works on more implementations. Carefully, Pierre -- [EMAIL PROTECTED] OpenPGP 0xD9D50D8A
signature.asc
Description: Digital signature
_______________________________________________ elephant-devel site list elephant-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/elephant-devel
