Ron Isaacson writes:
I've had quite a bit of trouble getting 21.5.29 working in our
environment. After comparing paths.h between 21.5.28 and 21.5.29, I
finally figured out why:
might short-circuit that a bit.
In the future, I'd appreciate it if this sort of thing were
highlighted right up top in the release notes, along with other things
that are important to your friendly neighborhood local maintainers...
I'll do what I can, but with two years between beta releases, I can't
really say I'm surprised something like that snuck through. I'm not
even sure that the actual change wasn't in 21.5.28 or even earlier;
the logs in 21.5.29 look like bugfixes to an earlier change.
You also shouldn't take the fact of a release or its absence too
seriously; compared to any given commit, the only extra QA that a
release gets in 21.5 is a guarantee that it builds, runs, and shows no
new regressions on my machines (Mac OS X with default GCC and Gentoo
Linux with GCC 4.2 currently) in my default configuration (with Mule,
X11, modules, debug, and error checking, and maybe a couple other
AFAIK, few of the active developers have the resources to regularly do
installs, so beta testing would be very helpful for this kind of
XEmacs-Beta mailing list