On Thu, Aug 26, 2010 at 4:20 PM, Graham Gower <[email protected]> wrote: > """if a build fails, then issues are reported, and the testing-testing > branch is moved ahead to capture fixes made in the dev branch. Once > the issue is fixed, all combinations are retested.""" > > Can I suggest that the testing-testing branch not be moved ahead?
I think yes the fixes should be committed to master and then pulled into the testing-testing branch IOW testing-testing moved ahead to new head on each monday and I think if you have successful build on prior monday and dont want to test it the tag should still be there. I think continuous build is the only way we can make sure that what we are committing is not breaking stuff. ideally testing branch should move every time a fix is committed upstream which was reported in testing-testing branch but Monday to Monday is ok too. Its > not really fair on testers to have to retest, especially if the branch > is moved ahead a couple of times. Obviously breakages should be fixed > and committed, but can't it just wait for the following week's testing > branch to show up as a successful build? > > -Graham > > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel > _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
