> I'm afraid that due to other commitments, I've been unable to do any > further work on the master branch for 4.0.0, and it's unlikely that this will > change in the near future. If anything, I'm unlikely to be able to spend much > more time on the project at all, and I might have to end my involvement > entirely.
That isn't surprising, but I appreciate the forewarning. That's why I didn't really favor trying to do a 4.0.0 originally, I just don't think there's enough long term resource commitment for that to be a wise choice. Were it my decision, I would post a warning that the code is being sunsetted and anybody on it should be getting off it. Which I think is pretty clear as it is, but it's the responsible and proper thing to just say so. > We do have a large accumulation of patches which would certainly be > worth carrying over to the 3.2 branch where applicable, Yes, that's my goal right now, within reason. I simply can't "fix" most things unfortunately because I don't know the code and the risk of breaking things is much higher than the payoff in most cases. > When it comes to ABI compatibility checking, I'll be happy to do runs of > some of the ABI checking tools to look for any compatibility issues with the > ABI or API, if you haven't already done this. My approach, as we've been debating, is just to avoid the possibility whereever I can by not touching headers, but I am willing to accept that I'm much more conservative about this than I should be and things may not work quite the way I've always thought they did. > It would be nice to get the CI fixed up again before making a release. > It's > probably not too difficult to get working again; the CI image and the build > logic probably need updating to cope with external changes which broke it > in the interim. I can try to find a bit of time to inspect this--it's not too > difficult, just takes time to wait for builds for each change to test it. I definitely can't spend time there, so if you can, that's great. If not, it's best to wind down anything I can't support unless somebody else steps up to take it over. Thanks for checking in. -- Scott
