Waiting for Emacs 22 (and looking forward to Emacs 23)
The low point was probably sometime around when Richard Stallman got tired of people asking when a release might happen:
A number of developers responded that they had no intent to insult or abuse, but that they do have real concerns about how the process works. A couple of examples:
(Kim Storm).
(JD Smith).
Clearly, the extended Emacs development cycle is proving frustrating for developers. The situation with the Linux kernel was once similar; changes merged at the beginning of a development cycle could take years to make it to a stable release. In that case, distributors responded by backporting changes into older releases, but that doesn't happen with Emacs.
The good news is that the biggest blocker - some questions about whether the Python mode code could be distributed by the FSF - appears to have resolved itself in the best possible way: the code has been cleared. Inevitably, there's another bug or two in need of squashing before the release can happen, but the remaining wait should be relatively short. Hopefully.
Some of the Emacs developers are already looking forward to the
Emacs 23 development cycle. One of the first things that may go in is
multi-tty support,
which allows a single emacs instance to drive multiple terminals or X
connections. This code apparently still does not work on all
architectures, though, meaning it needs some work before it is truly ready.
The other big change is a complete rework of character set handling; only
Emacs would come with a news item reading "The Emacs character set is
now a superset of Unicode. (It has about four times the code space, which
should be plenty).
" There's a lot of other work waiting to be
merged, but getting the unicode-2 branch and multi-tty working together
looks like it should be enough to keep the developers busy for a little
while. Happily, they are starting to think about this sort of challenge
rather than wondering if their previous work will ever be released.
