+* refactored in preparation for moving CLOS into cold init and merging
+ SB-PCL:FOO with CL:FOO (for FOO=CLASS, FOO=CLASS-OF, etc.)
+ ** systematized support for MOP (more regression tests, maybe)
+ to try to make sure things don't get mislaid in the
+ upcoming CLOS restructuring
+ ** extracted type system (and maybe CLASSOIDs) from SB-KERNEL
+ into new SB-TYPE package
+ ** reimplemented GENERIC-FUNCTION as a primitive object (or
+ maybe made SB-MOP:FUNCALLABLE-STANDARD-OBJECT the
+ primitive object, and then let GENERIC-FUNCTIONs
+ inherit from that) instead of structures with
+ :ALTERNATE-METACLASS and funcallableness. Now
+ FUNCALLABLE-INSTANCE can go away. (And now the new
+ funcallable primitive objects need to go into
+ collections like *FUN-HEADER-WIDETAGS* where
+ FUNCALLABLE-INSTANCE objects used to be.)
+ ** reimplemented CONDITIONs as primitive objects instead of
+ structures with :ALTERNATE-METACLASS. Now (between
+ this and the change to GENERIC-FUNCTIONs)
+ DEFSTRUCT :ALTERNATE-METACLASS can go away.
+ ** (maybe) Now INSTANCE_POINTER_LOWTAG can become just
+ STRUCTURE_POINTER_LOWTAG, and the concept of
+ SB-KERNEL:INSTANCE (including INSTANCEP,
+ (SPECIFIER-TYPE 'INSTANCE), etc.) can go away.
+* moved CLOS into cold init, in order to allow CLOS to be used in the
+ implementation of the core system (e.g. the type system and the
+ compiler) and in order to support merger of CL:CLASS with
+ SB-PCL:CLASS
+* (maybe) eliminated warm init altogether in favor of cold init
+* (maybe, especially if warm init can be eliminated) rationalized
+ the build process, fixing miscellaneous pre-0.5.0 stuff that's
+ transparently not the right thing
+ ** removed separate build directories, now just building in
+ place with .sbclcoldfasl extensions
+* (maybe) more refactoring in preparation for merging SB-PCL:FOO
+ into CL:FOO: reimplemented type system OO dispatch
+ (!DEFINE-TYPE-METHOD, etc.) in terms of CLOS OO dispatch
+* added some automatic tests for basic binary compatibility, in hopes
+ that it might be practical to maintain binary compatibility
+ between minor maintenance releases on the stable branch (but no
+ promises, sorry, since I've never tried to do this before, and
+ have no idea how much of a pain this'll be)
+========================================================================
+for 1.0 (fixes of lower priority which I'd nonetheless be embarrassed
+to leave unfixed in 1.0):
+* all too many BUGS entries and FIXMEs
+=======================================================================
+other priorities, no particular time:
+
+* bug fixes, especially really annoying bugs (ANSI or not) and any
+ ANSI bugs (i.e. not just bugs in extras like the debugger or
+ "declarations are assertions", but violations of the standard)
+* better communication with the outside world (scratching WHN's
+ personal itch): I don't want socket-level stuff so much as I
+ want RPC-level or higher (CORBA?) interfaces and (possibly
+ through RPC or CORBA) GUI support
+* Especially when ldb is not compiled in, the default "assertion failed"
+ behaviour in many parts of the runtime is unfriendly. It may
+ be appropriate to look at some of these and see if they can be
+ handled in some less abrupt way than aborting
+=======================================================================
+important but out of scope (for WHN, anyway: Patches from other people
+are still welcome!) until after 1.0:
+ * DYNAMIC-EXTENT
+ * sadly deteriorated support for ANSI-style block compilation
+ (static linking of DEFUNs within a single file or
+ WITH-COMPILATION-UNIT)
+ * various GC issues (exuberant cut-and-paste coding,
+ possibly dangerously over-conservative handling
+ of neighbors of function objects, general GC efficiency)
+ * package issues other than SB!TYPE, SB!MOP, and dead exported
+ symbols
+ * Any systematic effort to fix compiler consistency checks is
+ out of scope. (However, it still might be possible to
+ determine that some or all of them are hopelessly stale
+ and delete them.)
+=======================================================================
+other known issues with no particular target date:
+
+bugs listed on the man page