On Fri, Feb 18, 2011 at 6:28 AM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > On 2011-02-18 14:57, Simon King wrote: >> I could imagine that it would not be feasible to let the patchbot >> operate with a multitude of different sage versions. But perhaps it >> would be doable to let it work with *two* versions: 1. the latest >> release (default), 2. the latest alpha version. > > Why not *only* the latest alpha? That would make more sense to me.
Because 1) Some people, myself included, don't enjoy downloading and rebuilding every alpha that comes out and 2) While alphas are much more stable than they used to be, it's nice to start with a clean, known, working base. Remember how much less useful the bot was when everything had the same failing test (though eventually we could logic in place to let green be "no regressions with this ticket" rather than all tests passed). That being said, the patchbot is written as two separate components, the bot and the server. The intent is to ship the bot itself with Sage (maybe I'll get motivated enough to get it into 4.6.2) and so anyone can test tickets on any hardware they want. This will give us platform, hardware, and version diversity. There would still be a centralized server. (Well, people could run their own servers if they want, but that's not terribly useful.) The server itself is written to handle versioning, e.g. http://sage.math.washington.edu:21100/ticket/?base=4.6 - 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
