First, the patchbot is an excellent idea and will be a very useful tool. Thanks, Robert, for your work on it.
However, I have found myself wrestling with it a bit. I probably have some things confused below - corrections, clarifications or comments appreciated. 1. If the patchbot passes all tests for a ticket - then good. But if it fails, there can be a variety of reasons, like missing dependencies (on dependent tickets?) so a reviewer should not assume the absence of a green disk is a ticket that is not really ready for review. The patchbot is experimental still, no? 2. The release manager would like apply/depends information in the Trac description entry (at the top). The patchbot does not read these? 3. In the presence of several patches on a ticket, or other complicated situations, the patchbot uses the the last "Depends" and "Apply" strings it sees in the *comments*? 4. Patchbot will begin at the latest stable release, so dependencies need to be stated on dependent tickets back as far as the last stable release? 5. Looks like Martin D. is adding a "Dependencies" field to Trac. How about an "Apply" field, and this will all be in one place? 6. Is there a way to trigger the patchbot on a specific ticket? Otherwise - what type of edit triggers a run, and what sort of delay should be expected? 7. Documentation is at: http://wiki.sagemath.org/buildbot Thanks, Rob -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
