Hi, I would like to propose that we start getting ready for 3.1.0 and release the first candidate in two weeks time. This can then be followed by a month of public testing and, provided no major problems are uncovered, another vote and the final 3.1.0 release.
The two week period before the release candidate should allow anyone interested in fixing some bugs to do so. The current list of open bugs that are scheduled to be fixed for 3.1.0 is available via this URL: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10510&fixfor=12313294 Feel free to add other bugs to this schedule if you would like to fix them for the release. Note also that after the release candidate is published, only fixes for critical problems will be accepted. There is also the build matrix for all the supported platforms that we need to test before making the release. If you have access to some of the platforms, please consider testing Xerces-C++ and updating the matrix with the results. http://wiki.apache.org/xerces/XercescBuildStatus Finally, there are a number of old, unsupported, and unmaintained project files in the projects/ directory. Namely, BCB6, BCC.551, and VC6. I would like to remove these. Let me know if you have any objections and are prepared to make sure they work for this release and to continue actively maintaining them for future releases. Here is my +1 for the rc1. Boris -- Boris Kolpackov, Code Synthesis http://codesynthesis.com/~boris/blog Open-source XML data binding for C++ http://codesynthesis.com/products/xsd XML data binding for embedded systems http://codesynthesis.com/products/xsde Command line interface to C++ compiler http://codesynthesis.com/projects/cli --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
