#17898: Removal of wrong stopgap
-------------------------------------+-------------------------------------
Reporter: aschilling | Owner:
Type: defect | Status: needs_work
Priority: major | Milestone: sage-6.6
Component: combinatorics | Resolution:
Keywords: stopgap, | Merged in:
partitions | Reviewers: Travis Scrimshaw
Authors: Anne Schilling | Work issues:
Report Upstream: N/A | Commit:
Branch: | 39142901893bc0207e8271ccd4772469fe958e0f
public/ticket/17898 | Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Changes (by jdemeyer):
* status: positive_review => needs_work
Comment:
Replying to [comment:15 tscrim]:
> I also strongly believe this stopgap message, with all of the different
places this shows up across combinatorics, is very harmful to Sage.
Moreover #17637 was positively reviewed and merged very quickly (within 2
days IIRC) and as such did not receive the scrutiny that it deserved. As
such, this ticket is about returning to the status-quo where we can have a
discussion and proposals about a good solution instead of blindly saying
things may be wrong.
In #17637, we followed the correct stopgap procedure: somebody finds a
dangerous bug, a stopgap is created to warn people and ''in the mean
time'' (while the stopgap exists), people can fix the bug.
--
Ticket URL: <http://trac.sagemath.org/ticket/17898#comment:16>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
