Hello folks,
during my talk about the Sage development process I raised a couple of
issues on how we can improve the quality of Sage that have been
discussed in the past here in the groups, in IRC and also face to
face. I did end up making a wiki page at http://wiki.sagemath.org/QualityControl
Below is a list more or less copied from the presentation, but we
should definitely have a discussion about the list. Feel free to raise
additional points or suggest changes. Obviously you should feel free
to change the wiki page. The first three points on the list are
already submitted (at least in an initial version) and will hopefully
be merged by the end of Dev1:
* performance regression/timeit for doctests - #3476
* pickle jar - see #3482
* Patch Review Committee
* caching memory limit to prevent Sage gobbling up all system
memory
* turn caching on/off - maybe even by subsystem for error checking/
performance regression
* fine grained optional doctests, i.e. "Stein's Axiom I:
Everything not tested is broken"
* remove all "nodoctest" from the Sage library tree and fix
failing doctests
* more and better documentation of process, i.e. bundles vs.
patches, patch bombs, best practices
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
