On 5/26/10 2:59 AM, David Kirkby wrote:
I sometimes wonder if trac tickets should have a "risk factor"
attached to them. Something like
1)- Very low risk (Typos, documentation errors, numerical noise on doctests.)
2) Low risk. (Changes that occur on only one or two rarer operating
systems, or specific versions of specific Linux distributions).
3) Medium risk (Changes to the library)
4) High risk. (Updates of most standard packages)
5) Very high risk (Updates to standard packages which are used by many
people on all systems (MPIR, MPFR, Python etc) or if a new standard
package is added to Sage.
I would be willing to try filling out such "risk factor" fields in trac,
though of course, risk assessments also carry a risk factor.
Jason
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
