On 07/23/2015 11:14 AM, Brad wrote: >> I see Brad change the all behavior instead of fixing bugs . can't >> afford the time to play that game.. refer to Brad fro now on.. >> Changing behavior /doc and way of operating when seeing a bug is a >> receipt for never releasing/delivering .. > I have no clue what that means Nicolas. It does not translate very well. Yes I did have to revert some changes that you made because they were breaking the install. I'd be more than happy to help find solutions, but I don't have time to not have a working package. Please review the revision history and you'll see that they were merely commented out and can be re-added once they've been tested by multiple people. I think what Nicolas means is, for example, instead of documenting a "reboot" in the manual to fix a problem in the package/scripts we should be fixing/adjusting the package/scripts to solve the problem instead and if possible. I understand and appreciate your deadline of getting a working package for tomorrow & next week but I also understand and agree with Nicolas' frustration that it doesn't excuse us from properly fixing problems. My suggestion at this point is get a working package for tomorrow's deadline but schedule a mini-sprint ASAP so we can work this out. We could use next week's team time to discuss this if anyone's interested? > >> >> >> >> >> On Thu, Jul 23, 2015 at 1:30 PM, Zhanglei Mao >>