On Tue, Feb 2, 2016 at 11:54 AM, John Cowan <xxxxxx@mercury.ccil.org> wrote:
There is.  I wanted to mention the idea of having a more formalized Last
Call process, whereby Arthur (always willing to make more work for you,
Arthur!) would announce last call as widely as finalization, in hopes
that alternative implementations, typos, and other such problems would
surface just before rather than just after finalization.

It's a reasonable idea, and I'd be happy to do it, but we'll need to figure out what happens if non-trivial changes are made during the last-call period.  Do we reset from the last-call state to the draft state rather than moving to the final state?  And how do we decide what's non-trivial?

When I have a chance, I'll put together a proposal and send it to srfi-announce.  Suggestions welcome.