On 27 Mai, 00:52, "Dr. David Kirkby" <david.kir...@onetel.net> wrote: > On 05/26/10 09:48 PM, leif wrote: > > On 26 Mai, 21:50, "Dr. David Kirkby"<david.kir...@onetel.net> wrote: > >> On 05/26/10 05:34 PM, leif wrote: > >>>> I like the risk assessment field idea. > > >>> Me too, perhaps give it a different name. > > >> What would you call it? There are at least three things to consider I can > >> think of. > > >> 1) What are the risks associated with a change? > > > impact (quantitive; severity is too hard) > > >> 2) The probability of the change causing a problem. > > > ? at least *what* it might cause? Who knows... > > >> 3) The impact such a problem would cause. > > > affected components > > >> There might be others. > > > Yes. Just lost one. > > I don't follow you. What have you lost?
I simply had a 3rd/4th aspect in mind, but immediately forgot it. :( Perhaps one should also differentiate between the impact on users and that on the source code/development process. -Leif > Dave -- 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
