>>>> Stephen wrote:
Stephen> Requires a release manager, but given a release manager we
Stephen> can do that. IMHO there's a lot to be done, though. A lot
Stephen> of the attractive features suck. Eg, Xft's complete
Stephen> confusion in configuring fonts. We also really ought to
Stephen> consider a massive GNU sync if we want to recover any of the
Stephen> mindshare that that wiki page indicates we've lost.
Well then we should make a list with the things that really, really,
really needs to be fixed before we can release a new version. Kill
your darlings, be hard on ourselves.
> > - Go GPLv3 for the next release after that.
Stephen> I think this is actually the highest priority, as it prevents most
Stephen> people from doing any GNU syncing (althoug Aidan has demonstrated it's
Stephen> possible). It's also something that somebody other than Ben Wing can
can or can't?
This is one reason I think a release of 21.5 is a good thing. It will
be a good starting point for the GPLv3 version.
Stephen> Another problem is that many of them only can handle one
Stephen> display at a time AFAIK. Unacceptable to me personally, I'd
Stephen> have to stop using XEmacs! I suppose GTK can handle multiple
Stephen> displays by now? But how about the higher level toolkits
Stephen> like wxWindows? And do they flexibly allow input from other
Stephen> sources like background subprocesses and TTY displays and
Needs to be investigated of course. I have, as you might guessed, not
wished this based on technical considerations. I look at it from the
perspective that it seems hard to support so many different window
systems. We need to find a giant's shoulders to stand on here. If it
is possible of course.
If it is in conflict with XEmacs basic architecture we need to live
with that of course (or change it).
Stephen> This is hard. Slowness in extents is at a very low level in
Stephen> the code. The fastest way to get speed here may actually be
Stephen> to implement widechar buffers.
Feel free to change the plan then. We should not attempt to do hard of
impossible things that doesn't buy us something.
The beauty of a plan is that you only need to know the next
step. After that you can change it based on your new, and hopefully
better, understanding of the problem.
So my short revised plan is this: do everything that _must_ be done to
make 21.5 a new release, aiming at making the next release after that
a move to GPLv3 and, looking further, first after that a massively
XEmacs-Beta mailing list