Re: The future of XEmacs
Mike Kupfer writes:
Stephen J. Turnbull wrote:
> I'd really like to fix the damn progress bar crash.
Is this crash only seen in 21.5? If it's also present in 21.4, I
wouldn't make it a blocker for 21.6.
If we don't fix it, I'm going to remove it. It's getting reported
more frequently, although I'm not sure why. Maybe due to the increase
in ASLR systems, but who really knows.... Anyway, it's a bad thing.
The main reason I started using 21.5 was that I was getting more
email
that required decent UTF-8 support. It works well enough for my
purposes, but I concede that my purposes are pretty limited compared to
those of some other users.
If the current 21.5 is more likely than 21.4 to corrupt user files, then
I agree that's a blocker.
I think it is. The underlying problem, that the coding system code
will happily substitute a character (usually "~") for characters it
doesn't know how to encode, is common to 21.4 and 21.5. But 21.4 is
more accurate at detecting encodings, so this is less of a problem.
On the other hand, if the problem is just that the current 21.5
isn't as complete as we'd like it, I suspect we'd be better served
by cutting a new stable branch with what we've got.
Well, people who are already using 21.5 will be better served. But
people who are still using 21.4 and change to 21.5 experience a lot of
small regressions. Releasing 21.6 straight from the trunk as is will
make developers a little bit happier (but not much, there really is
very little restriction on what you can put into core or packages
based on 21.4 compatibility). It won't really change anything for
people already using 21.5, and I think it will make a lot of people who
switch from 21.4 to the new stable branch mildly unhappy.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta