On Sun, May 4, 2014 at 7:38 AM, Dirk Bächle <tshor...@gmx.de> wrote: > Hi there, > > I'm currently wading through our issue list at tigris.org, trying to clean > things up a little (closing resolved bugs and such...). Sorry, if this > creates some noise on the corresponding mailing list... > > I found issue #2739, which is in state "STARTED" but assigned to > "issues@scons"...so nobody effectively. I think that only "NEW" or > "REOPENED" issues should be assigned to "issues@scons", leaving the question > how to resolve this? Can someone take it? > > Further stirring up old topics ;), I pondered over the bugtracker migration > task again. For the issue interface to OpenHatch, I now have a bug importer > ready. It's capable of scraping our whole issue database (2947+ issues) from > tigris.org to a single JSON file in about 7 minutes. >> >> From there it wouldn't be much effort to push all the data via xmlrpc > > into a roundup ( http://www.roundup-tracker.org ) instance, for example. I'm > not sure what our options are for adding new "services" to our web hosting. > But roundup allegedly runs standalone, as well as via "mod_python", using > WSGI or through CGI. Maybe we could host this ourselves? > Even if it's just to get away from Tigris *now*...as a first step. We might > have to migrate further, later on. But then we're in a much better position > (Python-based tracker, support for xmlrpc) to pull all our data out again, > and convert it into a possibly new format.
This is a great start. Thanks for doing it! My preference would be a hosted bugtracker though, just because it's one less thing to manage (keep patched, ensure uptime etc.). Also, a minor point, but people may have more familiarity with the big hosted ones. Now, that said, I don't really have much experience with any of them that I like. So if roundup is nice, hosting it ourselves wouldn't be all that terrible. I'm pretty sure Pair, our current host, can do mod_python. Ideally we'd have a stable tracker so we could put bug links into commit messages, and mailing lists, and they'd still work 10 years from now. But that may be an impossible dream. :-) As for #2739, I see I was involved in that. I tried to get the OP to write a test but that apparently was pushing a little too hard for him at the time. I guess I should take it. The batch-mode fixes in there are quite valuable. -- Gary _______________________________________________ Scons-dev mailing list Scons-dev@scons.org http://two.pairlist.net/mailman/listinfo/scons-dev
