On Wed, Apr 10, 2013 at 10:57 AM, Eric Bénard <[email protected]> wrote: > Le Wed, 10 Apr 2013 10:48:31 -0300, > Otavio Salvador <[email protected]> a écrit : >> You are welcome to review the patches and test; I just cannot keep >> holding patches for so long as it is a nightmare to manage a huge >> queue of patches. Specially when they are tested and need more wider >> test. > > less then 24 hours between sending the match on the ML and comitting > them doesn't allow any serious testing by the ML readers.
Agreed. It was indeed less than 24 hours. Next time I will give 48 hours for huge or complex patchsets; I just don't see a reason to wait 24 hours for trivial bug fixes however I agree a U-Boot change needs more time and will follow this rule next time. > A few days doesn't seems "so long". >> If you look at the date of U-Boot commit you will see I've been using >> it for quite some time so I did compile the final patchset yesterday >> but been testing it. >> > If you expect peoples on the ML to test and give feedback, then you > need to give them a little bit of time. Agreed, read above. >> Another thing we need more people to be able to test the boards and >> report any regressions so it is harder to do when it is not in master >> (and autobuilder coverage). >> >> It'd be very good if you could give them a try and report any issues. > > It would be good to allow people to test _before_ commiting and not > after. I wasn't clear about what I meant. I mean that obviously the test we can do before having it used by everyone is a limited test and some subtle issues might be not discover until we have it with a wider user base. This was the reason I rushed (and I agree it was too fast) in this case. I think it is important to have time to iron out any possible regression not found in initial test; but I agree that waiting a bit of more time wouldn't change it. Regards, -- Otavio Salvador O.S. Systems E-mail: [email protected] http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br _______________________________________________ meta-freescale mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-freescale
