Hi all, FWIW, I'm +1 on doing the merge of unstable to trunk now. Whatever short-term items we need to handle can be done on the 2.7 branch; any remaining platforms can be worked out later. It'll be a fair while until we're ready for a 3.0 release anyway, I suspect.
Cheers, Neil Neil Graham Manager, XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] James Berry <[EMAIL PROTECTED]> 06/13/2005 08:51 PM Please respond to c-dev To [email protected] cc Subject 3.0 unstable branch update (Merge now?) Here I am again with my weekly check-in and query about the state of the 3.0 unstable branch. I've got the rest of this week in town before I'm out through mid- July. Do to that schedule, I want to see if we can get the 3.0 unstable branch merged to trunk during the next couple of days, in order that it doesn't diverge too much from trunk, and so that I can help with any issues that come up before I leave. Thanks to all of you, the 3.0 unstable branch is now more stable, though I'm sure there's still work to do. In particular Dave, Alberto, Axel, and Greg have all contributed bug reports and platform- specific fixes. Here's an update to the platform support (your feedback and corrections welcome): Configure/Build success: - Mac OS X 10.4 jberry (command line build, not XCode) - FreeBSD 4.11 jberry (minotaur.apache.org) - Mingw ver? amassari - cygwin Axel - SuSE Linux 9.3 Axel (gcc version 3.3.5 20050117 (prerelease) (SUSE Linux), GNU Make 3.80) - Solaris (ver?) Greg Franks (Sunpro compiler) - Solaris dbertoni (GCC -- with notes?) - Windows VS.net amassari The following are unknown, by me anyway: - AIX (issues, according to dave) - Unix Services for Windows (is that what it's called?) - NetBSD - OpenBSD - True64 Since we're building on many more platforms now, I propose that we now merge to trunk. My intent was not that we do all development on my temporary 3.0-unstable branch, but that we use it to get the thing buildable for many of our developers. Furthermore, I'd like to hold off making any major non-build-related changes on the unstable branch, so that it doesn't diverge too much from trunk. So my proposal in short form: - Merge 3.0 unstable to trunk, with your consensus, over the next couple of days. - Concentrate effort to fix any remaining non-building platform that is critical to developer progress. - Perform remainder of work for Xerces 3.0 on the main trunk. Feedback? James. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
