2 questions: - For a developer (or a tester, or a reviewer), how much of the workflow (synchronizing/merging in changes, preparing a patch or a series of patches, pushing/uploading those patches) will actually use the web-based UI you mention, and how much will still use the command line from the developer/tester/reviewer's dreamhack? - If (as it sounds from what you're saying), you're planning to deprecate the "upload patch to Bugzilla" step of the workflow, what replaces it, and how does that let a reviewer's see which patches are waiting for a review and attach said review to the patches?
no subject
- For a developer (or a tester, or a reviewer), how much of the workflow (synchronizing/merging in changes, preparing a patch or a series of patches, pushing/uploading those patches) will actually use the web-based UI you mention, and how much will still use the command line from the developer/tester/reviewer's dreamhack?
- If (as it sounds from what you're saying), you're planning to deprecate the "upload patch to Bugzilla" step of the workflow, what replaces it, and how does that let a reviewer's see which patches are waiting for a review and attach said review to the patches?