All, Are there any outstanding bug-fixes which haven't yet been looked into, but were at one point reported to this list? I've trawled through my own archives and fixed as many of them as I could find recently -- but there may well be other bugs lurking from distro maintainers from Gentoo, RedHat, Fedora, etc., which have yet to be forwarded upstream to here. If anyone knows of such things, please would they send them to this list? [1] That way they can be prioritised accordingly.
I'd like to propose (if it isn't already known) a strict freeze on FVWM's code -- where only bug-fixes are being committed -- and/or work that's explicitly going towards making 2.5.29 as close to a stable release as possible. I don't want to see another 2.5.X at all -- I'd like the next release we do to be 2.6.0 -- so to that end, my efforts are focused on doing just that. Might take a bit longer, but it's high time it happened. My own bug-list is getting smaller. The only outstanding bug I have is this one here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464366 I have a prototype using XIM (XmbLookupString() and friends) which seems to fix this, but I am considering it a too large a change for it to go into FVWM before 2.5.29 is stabalised. I am still pondering if there's any merit in me committing my stop-gap patch which fixes the above issue [2] for 7-bit locales only. Probably not worth it, it's too much of a bodge. There was also an FvwmIconMan problem with the weightings on window entries (See subejct: "FvwmIconMan weighted sortings") -- but since the blasted reporter didn't answer my repeated pleas, I'm dropping this until/if he or someone else suggestes it's still a problem. There's still a little bit of work needed on the fvwm-convert-2.6 script -- I've tested it with as many configs as I could find that weren't already fudges -- alas, it will be unable to convert everything -- the biggest annoyance is the module syntax: *FooBarCommand Option -> *FooBar: Command option ... but that would take a lot of work for not much gain --- annoyingly, the module communication code has yet to fully deprecate that. :P My only working prototype of converting the above syntax is sketchy -- it can only ever work if the original module line is written in CamelCase, but it's pointless to use it if it can still fall fail and get the conversion wrong, which is worse than leaving it in its current state, albeit annoying. I might just detect those instances where it's "wrong" and throw a warning to the screen instead. Kindly, -- Thomas Adam [1] Don't bother reporting Debain bugs to me, I am already very much on top of those. Ubuntu ones OTOH, are welcome. [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=9;filename=fix-menu-hotkeys-for-accented-chars.patch;att=1;bug=464366 -- "It was the cruelest game I've ever played and it's played inside my head." -- "Hush The Warmth", Gorky's Zygotic Mynci.
