Hi Michael, I guess this is a vote for the principle of a release? For that I'll give my +1; the release plan promises much-needed functionality, and the date looks reasonable to me. But from a process perspective, I think we'll need a formal vote for a release, once we have a fixed date and (virtually) all code is in the repository, open for all committers to inspect. Actually, we'll need to have this within the PMC, now that I think about it, since it's PMCs that need to demonstrate oversight over subprojects.
Does that make sense? Cheers, Neil Neil Graham Manager, XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] Michael Glavassevich/Toronto/[EMAIL PROTECTED] 05/10/2005 11:49 AM Please respond to j-dev To [email protected] cc Subject [VOTE]: Xerces-J 2.7.0 Release on Friday, June 24th Hi everyone, As with previous releases we need to formally show consensus that it is indeed time for a new release of Xerces-J (and I certainly think it is), so I'm asking the committers to vote. Here's my +1. Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- 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]
