> I would also like to suggest that we have all the infrastructure > issues worked out before we commit to migrating to Forrest. This > way we won't end up in a situation that Xerces-C++ 3.0.0 is right > now with autoconf where the person/people with the necessary > expertise is/are unable to commit time to finish the built system.
What's left to do? I know some platforms don't work, but honestly either the project supports those platforms or it doesn't. If yes, somebody on the core team has to be responsible for testing and maintaining them, and if not, you don't support them and they shouldn't hold up a release. It's not reasonable to me to hold up development for a platform or compiler for which nobody is donating time, a box to test on, or both. Put up or shut up basically. -- Scott --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
