At least a user could look at the list of bugs silently producing wrong answers:
http://trac.sagemath.org/report/79 I updated the list by manually looking at open tickets from #1 to #13345 and adding a stopgap marker 'todo' if required. Remaining task (I will do that): check open tickets #13346 to #19383 for issues silently producing wrong answers and add them to the list http://trac.sagemath.org/report/79 Jakob Am Donnerstag, 8. Oktober 2015 19:05:23 UTC+2 schrieb Nathann Cohen: > > Just to keep everybody aware of what is going on here: > > - I tried to add a stopgap on a code that returns wrong results > > - The stopgap was refused because it was "just before a stable > release" and people did not want to alarm the users by telling them > that Sage returns wrong results (even though it does) > > - Jeroen noticed that if we add the stopgap now, the same thing may > happen for the next release cycle (as we are not sure that it will be > fixed in the meantime) > > - Thus, they now decide that we will not add the stopgap at all. Ever. > > So, no stopgap. Let us not tell the users that we return wrong > results. Let them deal with the consequences. > > This enlightening conversation showing how trying to preserve our > public image can ruin a good software is available there: > > http://trac.sagemath.org/ticket/19302#comment:27 > > Nathann > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
