I'd be glad to hear any positive alternative suggestions for how we can get better at this stuff (without one of our number going round pinging everyone).
This is an old difficulty - on the old Friday calls the action list didn't get actioned :-( Working together on trunk is definitely the way to go, and it does mean that across the Java developer community we need to have a consistent approach to the dev process. We've talked about this stuff together, on list, and agreed how we'll do it .... What can we do to make this better ? Why isn't it already working ? Bfn, Marnie On Wed, Nov 19, 2008 at 11:08 PM, Robert Greig <[EMAIL PROTECTED]>wrote: > 2008/11/19 Rafael Schloming <[EMAIL PROTECTED]>: > > > I don't think this is feasible. Commits that are on the order of weeks > old > > aren't trivially revertible. The work to disentangle the commit from any > > subsequent modifications could easily be more work than simply doing the > > review, and in many cases would itself constitute a change requiring > review. > > This is a good argument for ensuring that people complete reviews promptly. > > RG >
