Changes between Initial Version and Version 34 of Ticket #5970


Ignore:
Timestamp:
Dec 23, 2011, 11:10:43 AM (11 years ago)
Author:
jdemeyer
Comment:

Replying to SimonKing:

I am very much sure that Jeroen said that this is the correct way to proceed: If one thinks that the ticket is a duplicate then you review it accordingly, putting it as "positive review". Then the RELEASE MANAGER (nobody else!!) closes the ticket by choosing the resolution "duplicate", if he believes that the reasons given in the review make sense.

True, but you forget one important step: you should put the milestone to sage-duplicate/invalid/wontfix yourself, so I know the intention is to close this ticket as duplicate and no patch should be merged.

Nobody except for the release manager should close or reopen tickets (with a few exceptions like spam tickets, tickets marked as duplicate by the person who reported the ticket and with no other activity).

And if it's a duplicate, it would be nice to add a pointer in the description to the ticket of which it is a duplicate of.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #5970

    • Property Status changed from needs_review to positive_review
    • Property Cc jpflori zimmerma vbraun added
    • Property Milestone changed from sage-3.4.2 to sage-duplicate/invalid/wontfix
    • Property Summary changed from [with patch, needs review] Weak references in Polynomial Ring cache to Weak references in Polynomial Ring cache
    • Property Priority changed from major to critical
    • Property Report Upstream changed from to N/A
    • Property Reviewers changed from to Simon King

  • Ticket #5970 – Description

    initial v34  
    1111}}}
    1212without running into memory problems.
     13
     14See instead #715.