Too tired right now...

[David Kastrup]

Ok, I am going to do the release tomorrow (or rather today in the
morning). I have added some warning blurb to the RELEASE file about
XEmacs 21.4.16. I wanted to add a package conflict warning with
XEmacs to the RPM spec file but forgot that we don't even generate an
RPM for XEmacs.

So it would appear that this is pretty much what we can do.

[Uwe Brauer]

David> Ok, I am going to do the release tomorrow (or rather today
David> in the morning). I have added some warning blurb to the
David> RELEASE file about XEmacs 21.4.16. I wanted to add a
David> package conflict warning with XEmacs to the RPM spec file
David> but forgot that we don't even generate an RPM for XEmacs.

Can't you just wait up to Sunday night, when 21.4.17 will be released?
(I have read all the threads about it.)

[David Kastrup]

Post by Uwe Brauer
David> Ok, I am going to do the release tomorrow (or rather today
David> in the morning). I have added some warning blurb to the
David> RELEASE file about XEmacs 21.4.16. I wanted to add a
David> package conflict warning with XEmacs to the RPM spec file
David> but forgot that we don't even generate an RPM for XEmacs.
Can't you just wait up to Sunday night, when 21.4.17 will be released?
(I have read all the threads about it.)

If you have read all the threads, you have also read the reasons I
gave why I don't wait consider waiting for 21.4.17 worthwhile. If you
have anything _very_ important to _add_ to that discussion, you better
do it _very_ fast (like in the next 10 minutes) since I have already
tagged the release, am in the release process and am merely doing the
dreaded "get-it-to-compile-and-retag" routine dance right now.

[David Kastrup]

Post by Uwe Brauer
Can't you just wait up to Sunday night, when 21.4.17 will be
released? (I have read all the threads about it.)

David> If you have read all the threads, you have also read the
David> reasons I gave why I don't wait consider waiting for
David> 21.4.17 worthwhile. If you have anything _very_
David> important to _add_ to that discussion, you better do it
David> _very_ fast (like in the next 10 minutes) since I have
David> already tagged
Yes I think so: I just checked the new pre- 21.4.17 (CVS) and the
problem seems *not* to be solved completely, :(
So please go ahead.
The xemacs shy groups problem needs further investigation, I think.

If there is indeed still some shy groups problem then it better be
fixed before 21.4.17 is released. If you have a test case failing
with pre-21.4.17, then better send it to the respective XEmacs list
_very_ soon and copy the AUCTeX list so that others can give feedback
whether this is indeed certainly a problem within XEmacs and shy
groups, and not AUCTeX. If there is a bug remaining, the XEmacs
developers will have to come up with a regression test as well as a
fix in short time, maybe postponing release.

And with regard to giving a reproducible bug test environment, I think
it is more an advantage than a disadvantage for the XEmacs people to
have a released version of AUCTeX as a fixed point for testing.

[Uwe Brauer]

David> Ok, I am going to do the release tomorrow (or rather today
David> in the morning). I have added some warning blurb to the
David> RELEASE file about XEmacs 21.4.16. I wanted to add a
David> package conflict warning with XEmacs to the RPM spec file
David> but forgot that we don't even generate an RPM for XEmacs.

Post by Uwe Brauer
Can't you just wait up to Sunday night, when 21.4.17 will be released?
(I have read all the threads about it.)

David> If you have read all the threads, you have also read the
David> reasons I gave why I don't wait consider waiting for
David> 21.4.17 worthwhile. If you have anything _very_ important
David> to _add_ to that discussion, you better do it _very_ fast
David> (like in the next 10 minutes) since I have already tagged


Yes I think so: I just checked the new pre- 21.4.17 (CVS) and the
problem seems *not* to be solved completely, :(

So please go ahead.

The xemacs shy groups problem needs further investigation, I think.


David> the release, am in the release process and am merely doing
David> the dreaded "get-it-to-compile-and-retag" routine dance
David> right now.