On Tue, Dec 7, 2010 at 9:18 PM, Dan Drake <dr...@kaist.edu> wrote: > Count me as another person really excited about the automatic trac > ticket test bot. It's great work. Good job, Robert! > > First, my proposal: we should call that bit of software "patchbot", > since it automatically deals with patches; the other buildbot > (http://build.sagemath.org/sage/) takes tarballs and builds them. Having > two completely distinct services both called "buildbot" is confusing. I > propose "patchbot". Thoughts?
I like patchbot as well, in fact that's almost what I called it the first time around. Tracbot implies that it's tied to trac, which it isn't necessarily. > Second, I have two patches on a ticket > (http://trac.sagemath.org/sage_trac/ticket/10440); one gets applied to > the Sage library, the other to the scripts repo. How do I tell > what-we-currently-call-buildbot where to apply patches? The patchbot works by creating branches so that it doesn't have to create a entirely new copy of Sage for every ticket. Of course scripts doesn't play nicely with branching, so it can't even handle this. Eventually it should be extended to handle the other repos and spkgs, but that's future work. (Note that this is yet another justification for moving the scripts repo into the main repository, even if you enjoy manually managing patches to the two distinct repositories yourself.) - 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
