On 25/09/14 19:45, Zygmunt Krynicki wrote: > [snip] > 19:40 <@zyga> the biggest thing that didn't go in (and wont anytime > soon) is manager.runner patchset > 19:40 <@zyga> where you could just manager.runner.run(job, context, ui) > 19:41 <@zyga> but that will go away along with the runner actually > 19:41 <@zyga> runner will be decomposed to a shell runner + logger and > a new class that interprets a job.plugin and converts that to a > sequence of commands > 19:41 <@zyga> (not shell commands) > 19:41 <@zyga> (ui commands) > 19:42 <@zyga> I realized that until we can kill checkbox-gui none of > this can result in removing code :/ > 19:42 <@zyga> so I want to reach parity ASAP and kill checkbox-gui > 19:42 <@zyga> one big problem to face is checkbox-gui requirements, > aka 14.10+ :/ > 19:43 <@zyga> we will have to spend some time to get the app to work with > 14.04 > 19:43 <@zyga> and put 12.04 SDK apps on life support (unless it can > run the same as 14.04 but I haven't checked) > > So there you have it. It is in my interest to totally kill off > checkbox-gui and the resulting piles of code we cannot change without > changing C++ and dbus. To make that happen we need to have > checkbox-touch (including pyotherside) that works on 14.04, and if > possible on 12.04). > > I'll handle pyotherside. If you love hacking after hours, I'd love to > know if we can get checkbox-touch to work on 12.04 + SDK ppa and > vanilla 14.04.
Having checkbox-touch working on 12.04 and 14.04 won't be enough, checkbox-gui has some features that are not in checkbox-touch (checking logs during the run, rerun tests, submit to C3, ...) I don't think that our priorities should be adding those missing features to checkbox-touch, but having a good set of tests for phones and tablets and a minimum working test runner for phone and tablets. We are very close to having that minimum working test runner, and that's fantastic, so we should be focusing next in having a good set of tests. The test runner is just a tool, what it really provides value are the tests themselves. We could discuss whether we should fork checkbox-touch from the main branch (or the other way round) if we want to have a repository that is cleaner and shows what we really want to achieve going forward, but I don't think that working in adding more and more features to the touch interface for checkbox would help us achieve our goals. Thanks, Ara. > > Thanks > ZK > -- Mailing list: https://launchpad.net/~checkbox-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~checkbox-dev More help : https://help.launchpad.net/ListHelp
