Hi Benson: I wouldn't call it a "snafu" - it's totally reasonable to expect there to be enough active PMC members to be monitoring any given subproject list to pass a vote, and one might argue that if that's NOT the case then the project needs to focus a bit more on oversight.
That said, I do think making sure to cc gene...@ws on VOTEs is still a good idea, both for archival purposes (easy to see all the project VOTEs in one place) and for ensuring a quorum. Thanks, --Glen Benson Margulies wrote: > Glen, > > I'm sorry about the 'general' snafu. The WS project structure is more > complex than some of my other haunts, and I forgot that there's only > one PMC for all the subprojects. > > --benson > > > On Sat, Feb 28, 2009 at 10:51 AM, Glen Daniels <g...@thoughtcraft.com> wrote: >> Hi Benson: >> >> Here's my +1, and perhaps it's a good idea for us to adopt a policy of >> cc'ing gene...@ws for VOTEs, since clearly not all PMC members keep >> current on commons-dev. :) >> >> Folks, please try out the release and VOTE early and often. >> >> Thanks, >> --Glen >> >> Benson Margulies wrote: >>> Fellow developers, >>> >>> I have recreated the proposed release artifacts for Xml Schema release >>> 1.4.4. You can find them in >>> http://people.apache.org/~bimargulies/maven_staging/. >>> >>> The 'fixed' list is now: >>> >>> WSCOMMONS-436 SchemaBuilder returns a null XmlSchemaAppInfo when >>> appinfo element without source attribute. >>> WSCOMMONS-378 SchemaBuilder::handleSimpleType() doesn't >>> call processExtensibilityComponents() for facets >>> >>> >>> I would be most grateful for some votes in the next 72 hours. >>> >>> Here is my nonbinding +1. >>> >>> Respectfully submitted, >>> Your Xml Schema 1.4.4 release manager, >>> benson