Hi All, Cantor, Scott <canto...@osu.edu> writes:
> So I'm inclined to do the very ugly work of figuring out what's > missing from the trunk and reviewing all the additional work > there that was done before the project went into moribundity, > and try and get a 3.2 out the door this summer. That would be great. Since we are sharing plans, we (as in Code Synthesis) are planning to package Xerces-C++ for build2[1] in the near future (but no definite time-frame). While I haven't looked into this closely yet, the options we consider range between just packaging it as is to pretty much forking it. The main reasons for forking would be: (1) to switch to git (life is just too short for svn), (2) to get rid of the Apache bureaucracy, and (3) rip all the legacy parts out and clean things up (maybe even switching to C++11/14). [1] https://build2.org/ Boris --------------------------------------------------------------------- To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
