[SciPy-dev] Scipy workflow (and not tools).

[Matthew Brett]

Hi,

>> Tests protect the user and the developer alike.  It is irresponsible
>> to carry on the way we do.
>>
> No it's not.

Scipy is rarely released.  David and Stefan are saying that it is very
hard to release.

It might be true, that continuing with the organic, 'add it if it
seems good' approach, will be fine.   But it might also be true that
it will make Scipy grind to a halt, as it becomes too poorly
structured and tested to maintain.

http://anyall.org/blog/2009/02/comparison-of-data-analysis-packages-r-matlab-scipy-excel-sas-spss-stata/

rates Numpy / Scipy / matplotlib as 'immature'.  This is mainly
because of Scipy, and it's fair.  It we want it to change we have to
be able to release versions that have good documentation and low bug
counts.

The choices we make now are going to have long-lasting consequences for Scipy.

I think our best guess, from what David and Stefan are saying, that we
need a change towards more structured process.  I stress the word
"need".  This doesn't seem surprising to me.   I think we've got to
listen to them, because they are doing the work of maintaining and
releasing Scipy.

See y'all,

Matthew