> I've been > thinking about writing something like this up for a while now, but > there's never enough time to do everything one wants to in Sage :) >
For the record, I'm in the process of writing a first system for doing this right now. It's mostly done (I can automatically get a string of patches from a ticket, merge, and test, then either delete them from the history or commit them -- thank you queues!), but it's far from perfect. I'm going to be using it tomorrow to merge the tickets with positive review, and I'm sure I'm bound to hit a few more bugs while I do that. I'm definitely really excited to keep hearing what people want out of such a system -- I'm just offering a heads-up, because I don't want someone else to sit down and re-do the same work I've been doing. At least until we decide that what I've done needs completely rewritten. ;) In particular, I'm really curious what people think the right interface for this is. I've done the following: I've written a bunch of utility functions (to grab patches from a ticket, download a list of patches to a temp dir, queue a bunch up, etc.) that I've put in the sage library itself, since they seem like they'd be of independent interest. However, the process of rebuilding and testing sage seems unnatural to run from sage -- not impossible at all, just unnatural (at least to me). So I've written a shell script that loads just the utility file from the sage library, parses some command-line arguments (with getopt), and then runs the process non-interactively. This will work fine for a first go-round, but what do people want in general? I feel like the process of "download patches from a ticket, apply in some order, rebuild and test, and commit" makes sense as a menu-based text interface, especially if you want to do several in a row. Or am I the only one that likes that idea? I did spend too much time on MUDs in high school; maybe it's the reason I seem to want to turn release management into a text-based adventure game. "You are in a dark room, facing a massive patch bomb. Run, fight, or merge?" ... -cc --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
