My email service was interrupted a day or two ago but, after implementing a temporary workaround, everything I may have missed appears to have been delivered. Just wanted to let you know I didn't run off and disappear.
After catching up on all the mail, there's just so much, I don't know where to start. First, thanks for the PMC votes. Just to eliminate any possible ambiguity, I gratefully accept membership and all the associated responsibilities. Next, given that the PMC is responsible for approving releases, next week I'll brief the PMC on the status of jakarta-oro, the need for a 2.0.8 maintenance release, and ask for a vote so we can get that out the door. After that immediate need is satisfied (assuming it all goes through), if a consensus hasn't been reached on a policy for "maintenance mode" projects, I'd like to act on some of the suggestions put forth, starting by consulting with the jakarta-regexp committer(s) and moving from there. Even though jakarta-oro is stuck in maintenance mode, it has the potential for feature-enhancing development, but we need to increase the committer pool for that to happen. I've pretty much only been handling bug reports and prodding people who suggest enhancements to submit patches. I know Mark Murphy is interested in helping advance development, but I haven't heard from Takashi Okamoto for a while so I will track him down to see if he intends to remain active with the project before officially nominating him as a committer. Even if jakarta-oro remains in maintenance mode, an ASF-compliant procedure for maintenance releases needs to be enacted (presumably, the PMC vote alluded to above). Resolving bug reports in a timely fashion has never been a problem, but packing up releases has been. I believe jakarta-regexp has had at least one recent inquiry about when the next release will be made that incorporates the slew of bug fixes Michael McCallum and Vadim Gritsenko have made over time (haven't seen Michael commit anything in a long time though). I guess I'm looking for some confirmation of or pointer to the proper ASF-compliant release procedure. daniel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
