Sorry if I wasn't clear, the package maintainer must of course make sure that the doctests pass. Usually there are some minor changes, e.g. we do doctest the GAP version number which will always change. Or the output order of the upstream source changes. That does require some good judgement to verify that the output is still correct, but is there anybody who is better qualified to check that than the spkg maintainer? An really subtle bugs will only be found when the code is actually used, not by having it bitrot on a trac ticket.
On Friday, July 5, 2013 11:17:40 AM UTC-4, Simon King wrote: > > If I am not mistaken, the last version bump of Gap gave rise to several > doctests that needed to be fixed. At least, in my p_group_cohomology > spkg, I needed to fix stuff because of a change in some random generator > in Gap. > > So, a version bump requires at least a "make ptestlong" check. > -- 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/groups/opt_out.
