I did push component, receivers, etc to release since I expected
Chainsaw to be pushing for a release and they'd be done
simultaneously. However, there has been no chainsaw commits since
the log4j 1.2.15 release. I think we should at least get the
temporary encoding fix on UTF-8's and we need address the tarball/
webstart/apache release process issue, but I don't know what other
items are blocking a Chainsaw 2.0 release. Maybe we can talk about
it here and then someone can log a bug report for the release and
connect the blocking issues.
I'm hoping to have a crack at the encoding issue today. I don't think
there's anything else pressing other than the release process itself.
I would assume that we'd do log4j 1.2.16, extras 1.1 and jul-log4j-
bridge at the same time.
Sounds good.
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
