On Saturday, July 9, 2016 at 5:17:48 PM UTC-5, Jakob Kroeker wrote: > > Please don't. That field is suppose to be used for tickets which implement >> the stopgap when it is applicable > > > Unfortunately stopgaps for all the silent wrong results will hardly be > accepted. >
That's just not true (just don't make it so the message gets printed on input where we know the code works). > I already experienced heavy opposition as I created some and was not able > to create them in full extent. > > With labels on issues with silently wrong answers we will have at least an > up-to date list of them: > https://trac.sagemath.org/wiki/TicketReports > <https://www.google.com/url?q=https%3A%2F%2Ftrac.sagemath.org%2Fwiki%2FTicketReports&sa=D&sntz=1&usg=AFQjCNEtkT4Uut2F5tK1eMcnblcSzad-jA> > > And of course it is possible to create all the stopgaps afterwards. > > All you need to do is create a ticket that says "Stopgap for ticket #XYZ" and link it to the corresponding ticket, which takes almost no time. The description you added to the stopgap is already something in the ticket description. BTW, stopgaps are hardly an extreme tool unless you use them extremely (as one person had in the past). Plus, if you add a stopgap correctly, which usually doesn't take much time, then it makes it easy for people to review and add it into Sage. Best, Travis PS - Thank you for looking into these tickets. -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
