Hi Robert and all, On 17 Mrz., 08:15, Robert Bradshaw <rober...@math.washington.edu> wrote: > The only reason as far as I know that closing a ticket is the job of > the release manager is to make sure the code is actually merged (it is > left open 'till that point). I don't see any reason other's can't > close duplicate, won't fix, invalid, or otherwise resolved tickets > where no further action needs to be taken.
On the ticket, Jeroen (as release manager) pointed out what to do in this case: Give it a positive review *and* change the milestone to sage-duplicate/ invalid/wontfix/ ! I think that makes very much sense. It is a positive review, thus, the release manager becomes aware of it, and the milestone indicates that the ticket should be closed without taking further action. Cheers, Simon -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
