On Thu, 2014-01-30 at 10:23 +0000, Barros Pena, Belen wrote: > I'll try to speed up the review process. The problem I have is that, in my > experience, it pays off to fix as many issues as possible before merging > to a master branch (toaster/master in our case). The moment code is merged > to master, it seems to become necessary to raise issues using the bug > tracking system, which results in the number of issues ballooning up. I > don't have a problem with that, but people having to fix the issues might > find it difficult to decide what to do first: fixing problems from > previous features or tackling new features. > > I am copying everybody because this is very much a process problem: it > would be good to hear what everybody else thinks.
FWIW, my take on this is that: There is no hard requirement to have a bug open against an issue in master. In particular, if you find an issue and have a fix which gets sent out quickly, there is no point in taking the process overhead of opening the bug only to close it again. Equally, if there is a bug found in master and you don't have an immediate fix, we do prefer to open bugs to ensure the issue does not get forgotten about. Cheers, Richard _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
