Carsten, Jörg,

any chance to get the commons-logging bridge into that release (EXLBR-28)? 
Especially since I expect the next release not within the next 12 months ... ;-)

And I found out today that I also forgot to add some new things to
excalibur logging.

How do we handle these two requests? I personally would say, let's add
them and then build a new rc just for logging. WDYT?
I personally have no big issues with turning the crank one more time for RC3. If we were to do it, I'd probably do the all the dependencies, and not just logging, since the purpose of the RCs are to catch issues with integrations as well, right?

But, here's my question: what says we will not have some more additions after RC3? Can we get some agreement that even if there are worthwhile additions after RC3 they must wait for the next release?

Also, on the thought of releases, I don't think we will wait 12 months again. Personally, I plan to watch for project.xml(s) changing, and watch to see we don't get out of whack dependency-wise across modules. If we do that, then turining out a release frequently isn't really that much of a problem, as long as changes are supported by tests, and the community wants the releases.

Anyway, I'm +1 for RC3, as long as the community backs me up when I become a hard-ass post-RC3 :-). Also, if you get the checkins done by this week, then I'll make RC3 release on 21st, and still ask for final release vote (on 22nd) for 28th.

Shash


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to