This bug is purposefully not filed in Release Engineering to avoid confusion. It is about providing user interfaces that will use whatever protocol comes out of bug 1262165. Possible examples include: 1) The existing try syntax 2) A curses UI 3) A web form 4) Treeherder improvements Not only will we be able to schedule jobs, but we'll be able to determine *how* jobs are run (e.g test paths, environment variables, command line flags, etc). The user will potentially be able to enter in a lot of information, and whatever UI they use will need to support everything while still remaining intuitive.
You need to log in before you can comment on or make changes to this bug.