Now that version 1.1.5 has been released, it now makes sense to look
at what features need to get in in order to get version 1.2 to being
"release-ready."

A number of things complained about were consciously left alone
because, in the "stable" stream, we should (arguably) primarily be
fixing specific engine problems being experienced that _don't_ point
to major reimplementation of things.

In order not to invalidate RPM packaging work, for instance, we didn't
take on some of the build environment changes that got suggested,
notably cleaning up the usage of --prefix and other configure-time
parameters.  It is now "fair game" to do so; we'll presumably break
the RPMs, but that's necessary to clean things up.  Bugs #1507, 1508,
1509, 1510, 1497, 1473, 1475 all seem to be relevant to the build
environment.

Other things likely on the 1.2 "track":

- The stored function that regenerates sl_listen needs revising
  (#1485)

- EXECUTE SCRIPT will fail if an early query creates columns on
  tables, and then later queries manipulate those columns

- Rotating periodically between sl_log_1 and sl_log_2 will resolve
  some issues relating to XID rollover

- I'd sorta like to have EVENT PING, that sends a "chain letter" to
  the nodes so you can watch a 'custom' event propagate thru logs

- I favor a SUBMIT NOTIFY; Jan has a thought of having a EXECUTE UNIX
  SCRIPT where an event would pass along the name of a script to run
  on each node at the common point in the transaction stream

- More tests, more tests...  Someone ought to write... more tests...
  (Part of the point: someone _OTHER THAN I_ should write some more
  tests...)
-- 
output = ("cbbrowne" "@" "acm.org")
http://cbbrowne.com/info/spreadsheets.html
Idiosyncratic indentations, double-spacing, capitalization, etc., while
stamps of individuality, leave one an easy target for parody.
-- from the Symbolics Guidelines for Sending Mail