On Jul 22, 2005, at 6:36 PM, Yoav Shapira wrote:
Hi,
I think we're being a little conservative: call the next one a
beta, and
hopefully we'll get more user testing and feedback ;) But either
way a new
build is welcome.
As long as beta does not imply that the API is frozen, I'd be willing
to call it that. Especially if we included a list of things that
were likely to change. However, there are a lot of new and changed
API that should be reviewed before locking it down.
It does need a vote and the PMC needs to be the final arbiter of what
Logging Services releases, but I don't see why we can't do concurrent
log4j-dev and PMC votes until we can streamline the bylaws. Announce
the vote on both the PMC list and the log4j-dev list and have all
voting on the log4j-dev list, count all the votes from the log4j-
committers and then all the votes from the PMC members. Hard to
imagine a scenario where they'd differ.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
