> My position is the same: I don't mind having Xerces-P be part of > the distribution if we have someone to maintain it. I, however, > do not want to be forced to run extra tests every time I change > something
Seems like that's what having a maintainer implies, somebody to do that periodically. > 2. Before the release, if something is not working in swig, we > ask all interested parties on the mailing list to fix it. If > this does not happen we move swig to the attic and release > this version without swig. > > 3. If at some point we get someone interested in getting swig > back into shape, we move it back from attic to trunk. The problem with this is that people can't depend on having it maintained, so it won't be used. It becomes a self-fulfilling situation. > To make it clear, I don't have anything against Xerces-P or swig. I didn't have anything against all the various options and platforms either, but when I noted that it seemed like the project either had to have maintainers step up or drop them to get 3.0 done I was accused of heresy. Still seems like common sense to me. -- Scott --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
