Yes, there is no rush on the 4 alpha release - as you say, we know there are parts incomplete - but I figure the sooner we have something more concrete the more feedback we'll get on what is still to do. For your 1 and 2a fixes, if you have a partial fix but no time, perhaps try to make it available somehow and one of us can see if we can complete it. Worse case, we have to wait until you have more time, so we'd be no worse off.
Cheers, Paul. On Thu, May 14, 2020 at 3:57 PM Jochen Theodorou <blackd...@gmx.org> wrote: > On 14.05.20 03:58, Paul King wrote: > > > > Hi everyone, > > > > I was going to volunteer to prepare the next releases in a couple of > > days. Definitely 3.0.4, probably 2.5.12 and maybe our first alpha of 4.0 > > if I get time (or I may kick that off immediately after the others are > > complete). > > > > Time to get in any bug fixes you want for those releases. Please also > > let me know if you have any issues with the proposed timeframe. > > for 4.0... I mean ok, it is an alpha, but that log4j issue I looked into > revealed two problems: > (1) The build is not completely done with indy. Which means the tests > are not testing indy 100% > (2) After fixing that I found issues with indy that needs to be fixed. > Among these are > (2a) inner classes that get not initialized before we ask their meta > class for static method invocations and properties. And > (2b) An obscure problem with categories > (2c) maybe more > > I wanted to make a new branch with the fixes (1 and 2a are fixed so > far), but I ran out of time and I do not know when I get time enough to > fix these. > > bye Jochen >
