[SciPy-dev] The future of SciPy and its development infrastructure
Travis E. Oliphant
Fri Feb 27 00:00:49 CST 2009
Stéfan van der Walt wrote:
> Hi Travis
> 2009/2/27 Travis E. Oliphant <email@example.com>:
>> My biggest concern is having a bunch of code sitting in a
>> queue and not reviewed, nor committed --- or the review processes become
>> too onerous and code not making it through because of what I would
>> consider to be "ticky-tacky technicalities."
> That's a very valid concern. David and I are experimenting with
> different issue trackers and plugins for trac, to see how best to
> generate a "review pool". I.e., what I'd like to see is that, if you
> only have 5 minutes to work on SciPy in the evening, you can
> a) Go to trac and click on "tickets for review"
> b) Review a couple of tickets
> a) Go to trac and click on "reviewed tickets"
> b) Apply those patches
> a) Go to trac and click on "unresolved issues"
> b) Fix the bug
> c) Upload the patch for review
> Technically, (c) is a bit challenging. I note your concern that it
> would become difficult to check in, so what I would like is to have a
> script such as
> scipy-submit -t 212 -m "Do not deallocate memory after object disposal."
Something like that would be nice!
Thanks for the continued effort at improving workflow.
More information about the Scipy-dev