On Jan 21, 3:30 am, "Nicolas M. Thiery" <nicolas.thi...@u-psud.fr> wrote: > Hi! > > First thing: Robert, thanks so much for the buildbot. You are saving > all of us hours and hours of work! > > On Fri, Dec 03, 2010 at 03:12:48PM -0500, Jason Bandlow wrote: > > Huge +1 to this. Thank you very much for putting this together! And I > > like your (initial?) solution to the problem of not having a trac field > > for which patches to apply! > > Speaking of which: someone knowledgeable, please, please, please add a > field for ticket dependencies. This is a standard plugin of trac, and > the installation seems rather trivial: > > http://trac-hacks.org/wiki/MasterTicketsPlugin > > I would also very much vote for adding a trac field for which patches > to apply in which order. > > This would make things easier (no convention to lear) and more robust, > both for the ticket readers and writers, and for scripts.
Except for the fact that the buildbot currently seems to do a recursive dependency thing. So it (according to comments other have left on tickets) will parse "depends on #1, #2, and #3" as meaning it applies #1, then looks at #2 (which itself says, "depends on #1"), applies #1 again, ... or something like this. Most humans would have just done #1, #2, then #3. So let's make sure that if any such fields are added, then both humans and bots know exactly which tickets and patches to apply in which order, and that this is clear on the label of the field. - kcrisman -- 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
