SL Baur <steve(a)vmailer.xemacs.org> writes:
One possible way is to split the development trees such that we have
a rigidly controlled stable branch (21.x) and a no-holds-barred
development tree.
I am not sure what you mean by this. I would prefer to see
"semi-stable" releases followed by fully stable releases. Example:
21.1 == bugfix of 21.0; however, 21.2 == 21.1 + portable dumper + ...
This doesn't mean that 21.2 has to be totally unstable, or
no-holds-barred.
I have tentatively approved Michael Sperber's plan for
addressing
Lisp Engine updates. As I understand it, it does not involve
commitment to anything specific until all the issues have been
hashed out.
If it doesn't involve commitment to anything specific, then what is
Michael's plan, exactly? I'd like to know what we are agreeing with,
if anything.
--
Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
"A Real Programmer's code can awe with its fiendish brilliance, even
as its crockishness appalls."