On Sat, Mar 3, 2012 at 12:15 PM, Michael Orlitzky <mich...@orlitzky.com> wrote: > On 03/02/2012 02:29 PM, kcrisman wrote: >> >> >> IF the patchbot actually applied the right patches to the right >> development version, naturally, which I suppose is what you mean in >> the next line? >> > > I meant that it would suck if the patchbot marked a ticket "needs work" > because e.g. it ran out of memory.
For sure, though defining the "development version" is currently problematic as well. But on this note, though I had originally intended it to do stuff like update the status in trac, as I worked on it I realize that it's not really that helpful to do so, and makes the system much more brittle in the case of incorrect/missing specification. What is important is being able to easily tell the status of a ticket by looking at it, which the colored blob currently does. The thing that is missing is (email?) notification, perhaps if it posted a comment on the ticket for the results of a run that would do the job. Once we get this into Sage it'll be a lot easier for people to make these kinds of improvements (well, maybe, I'll feel free to file pull requests on https://github.com/robertwb/sage-patchbot/.) - Robert -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
