Hi Scott, 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. I'm no longer actively using Xerces-C++, since the projects I used it for have wound down. I don't think there are any particularly compelling features on the master branch which anyone would miss. It was primarily some cleanup to remove obsolete stuff and bring it up to date with modern C++ standards in a very limited way. While it would have been nice to continue this and make a 4.0.0 release, I'm afraid I will have to leave this to someone else.
We do have a large accumulation of patches which would certainly be worth carrying over to the 3.2 branch where applicable, so I'm sure a point release with these fixes would be much appreciated by the wider community. 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. 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. Kind regards, Roger > -----Original Message----- > From: Cantor, Scott <canto...@osu.edu> > Sent: 05 October 2022 14:57 > To: c-dev@xerces.apache.org > Subject: Prepping a 3.2.4 release > > Resending... > > As the traffic indicates, I've got a rare window to actually do some work on a > release, so I'm aiming to get a 3.2.4 patch done quickly. > > I do not have the cycles or the will (or believe it's in the interest of the > project) to get a 4.0 out so I'm not working on that. > > I need to get my arms around what's actually committed on the branch and > what might be left to commit that's safe to do, so I'm starting there.
