Is a subproject entitled to make such decisions ? Anyway, I'm all in favor for a relaxed RTC, i.e. one should send a mail to the dev list annoucing what he is doing when working on big changes / new features. Lazy consensus seems the right thing for xbean to me.
For example, I guess that my last mail to this list was lost, or that nobody had any strong objections about using qdox 1.6 which has been compiled with jdk 5. This would make xbean-spring tied to jdk 5 :( On 8/23/06, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
Geronimo is considering a change to its review and commit policies. As a subproject, I think we should discuss how we would like to handle reviewing code and when it should be committed. So... How do you think we should handle this process? What rules-of-thumb should we use to guide ourselves? -dain
-- Cheers, Guillaume Nodet
