On Tue, Mar 5, 2013 at 2:36 PM, David Holmes <david.hol...@oracle.com>wrote:
> > Sorry but that is completely unacceptable. If you are providing changes > that obviously impact multiple platforms (ie there are platform specific > changes) then they _must_ be tested on all platforms. If the external > author/committer can not do that then they must work with someone in Oracle > who can assist with JPRT runs etc. There's always a tradeoff between agility and not breaking other folks. IMO the right approach is to improve processes so that bad commits don't cause other developers to lose time. Once upon a time, I was actually the tl gatekeeper and I implemented such a system. Today, I see there's a tl-gate, but there's close to zero testing between submission to tl-gate and "promotion" to tl-proper. In the system I implemented, there was a full build/test cycle in between.
