Protocol for when you see a ticket describing a bug that doesn't seem to exist in the current version

[Mahathi Vempati]

Precisely the title.

How do you go about closing a ticket if a described bug doesn't seem to exist anymore?

[Dima Pasechnik]

set the milestone to duplicate/invalid/wontfix
and give it positive review, with an explanation in a comment.

On Tue, Jan 14, 2020 at 5:53 PM Mahathi Vempati <maha...@gmail.com> wrote:
>
> Precisely the title.
>
> How do you go about closing a ticket if a described bug doesn't seem to exist anymore?
>
>

> --
> 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+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/81d6f5ba-230d-4b1b-8845-f242fbc56d55%40googlegroups.com.

[Mahathi Vempati]

Okay, will do. Thanks! 

To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq2zs3SyUS%2BU%3DDbvun4M1NkSvjw-RJBCJrUCv9c502miXQ%40mail.gmail.com.

[Nils Bruin]

On Tuesday, January 14, 2020 at 10:08:36 AM UTC-8, Dima Pasechnik wrote:

set the milestone to duplicate/invalid/wontfix
and give it positive review, with an explanation in a comment.

Depending how striking the claimed bug is, it might be inspiration for a good doctest, in which case the ticket can be used to actually "fix" the documentation.

[kcrisman]

set the milestone to duplicate/invalid/wontfix
and give it positive review, with an explanation in a comment.

Depending how striking the claimed bug is, it might be inspiration for a good doctest, in which case the ticket can be used to actually "fix" the documentation.

Yes, I strongly recommend putting a doctest in unless it is truly a trivial bug. 

[Emmanuel Charpentier]

Seconded.

If you haen to have sufficient ressources (a spare machine with a development tree), it might be worthy to bisect between the bug report and the current release to see *when* and *how* the bug was unintentionally fixed. This might help to build a relevant doctest.