On 26 Mai, 21:50, "Dr. David Kirkby" <david.kir...@onetel.net> wrote: > On 05/26/10 05:34 PM, leif wrote: > > > On 26 Mai, 18:09, Robert Bradshaw<rober...@math.washington.edu> > > >> 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. > Even things that have a fairly high probability of causing a problem are > probably not worth worrying about too much if the impact would be minimal. Such as not being functional on an obsolete platform ;-) > Conversely, even something which has a low probability of causing a problem, > but > would have major consequences, needs to be taken seriously. Yes, as Robert B. stated in another thread, a minimal "not hard" (1 character) change can have big consequences... :) (So it might be "trivial" as well as "critical".) > However, unless there was a *major* change in Sage release practices, it would > be a bit pointless doing any sort of risk analysis. I don't detect much of an > appetite for a major change in Sage release practices. In fact, I detect quite > the converse. Looks like... (I personally would replace many Sage "releases" by commits to the central repository, which should be a developer's resource, as opposed to "true" releases (including betas) for end users. IMHO some tickets are merged into "releases" too early, others too late. The notion of "alpha" releases is also different in Sage; have there ever been betas? ... Intermediate releases and their download could be avoided/replaced by just announcing which tickets will be/have been merged, s.t. a developer (more or less automatically) only updates the parts he's working on if appropriate.) -Leif -- 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
