Dear Steve et al,
On Sat, Sep 6, 2014 at 1:48 AM, Stephen J. Turnbull <stephen(a)xemacs.org> wrote:
Vin Shelton writes:
Given the lack of response, you would be entirely within your rights
to declare that you're retiring after 21.4.23, and make a last call by
yyyy-mm-dd declaration. (You could declare immediate retirement, too,
but I'd whine quite a bit about that since there are a few patches
remaining in the pipeline. ;-)
OK. 2014-12-01 will be the EOL for 21.4.xx. I will release 21.4.23
sometime before then, and I might release 21.4.24 on that date if some
pressing issues come up, but I'm don't think that's likely at this
> First off, src/ChangeLog says this:
> 2012-07-12 Vin Shelton <acs(a)xemacs.org>
> * glyphs-eimage.c: Fix this so it compiles with libpng-1.5.10.
It does now, after a fresh clone. "hg pull -u" in an older clone
didn't pull that in. :-(
I wonder what the contents of your older clone was? Was it perhaps
tied to 21.4.22? I'm glad the code is in hg, however.
> Secondly, I have no objections to patches to fix this and the
> 3.4 issue you identified elsewhere,
I'd like to fix this bug, too. I've made progress on localizing it
but don't have a fix yet.
Just to clarify, "this bug" means the file corruption using utf8 and
mule-ucs on 2^16 byte boundaries, right?
Sure. We can promote 21.5 to 21.6 and release it. Let me roll one
last beta next weekend and we shoot for a (US) Thanksgiving release,
That's a good timeframe from my POV.
When would you want to release 21.4.23?
I was thinking October [ 2014 :-) ]. Do you think you'll have a patch
ready by then?
As I mentioned above, there might still be a 21.4.24 if there are any
loose ends to tie up. If that's the case, I'll make a 21.4.24 release
early in 2015.
I don't much like that because essentially no work has been done
usability (fontconfig configuration being the biggest pain point, but
many users would like to see a GTK3 port (GTK3 programming makes me
barf, if that's the way we're going to go I'll help but really would
rather not lead), there remain display glitches with Xft, there are a
lot of rough edges in Mule which probably affect only me these days,
and so on). But the alternative is no better, given that the work
described isn't likely to be forthcoming in large quantity any time
Given the state of where 21.5 currently is and where we would like for
it to be I agree that this choice isn't ideal but I think an official
release of the 21.5 codebase very soon is essential if we want XEmacs
to continue to exist.
I would say that 21.7 development should be officially focused on
supporting upgrades to the packages. After that the work would be on
porting Emacs features. If people want to work privately on their own
features, fine, but at this point I think we need Emacs compatibility
improvements more than anything else.
Sounds like a plan.
XEmacs-Beta mailing list