> Some projects, with gcc being one example I believe, have "expected failures" Whilst not executing tests which display bugs might be attractive to some, I think it would be better to execute the test and report the failure as an expected failure. There is more chance someone will fix it then.
I agree with that. Ideally, I would like to be able to add broken doctests to Sage. Perhaps we should flag them with a trac ticket, so that the release manager knows that it has been reported already ? Perhaps we should also be able to add broken doctest, and the next release cannot be made while the bug has not been fixed.... Would mean that any bugfix is a blocker. Well. I think that it is extreme, but that being to boast that *ANY* bug is a blocker and that we fix them all is really worthwhile. Some people here say from time to time that Sage should fight the existing proprietary softwares more directly, and something like that is a HUGE plus. 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.
