I agree on the rollback strategy but you have to also realize that some
of the subsystems such as security cannot test infinitely before
checking in. It is like making a 1 line change to the code in 15
minutes and spend 4 days testing around to ensure not cause
regressions. I am talking out of experience here with the AS5 workspace
and security updates.
If you are callous and regularly cause regressions, then you need to be
thumped. ;)
Manik Surtani wrote:
+1. Well done. :-)
On 4 Apr 2009, at 00:21, Bill Burke wrote:
> Excellent job! (I'm not being sarcastic!) This is what a stable
> trunk is all about. Continuous stable commits.
>
> This process works. Believe me. Once people find that their stuff
> gets rolled back and they have to redo their work all over again,
> they'll be a lot more careful about committing.
>
> Jason T. Greene wrote:
>> Hi Everyone,
>> Since the leak issues are expected to take a few more days, and are
>> starting to affect our ability to get reliable test results, I have
>> reverted AOP back to 2.0.1, and restored the previous AS integration.
>> I also backed out the JTA update from GA to CR1 for the time being,
>> as we started seeing TCK regressions.