Bug reports that need to be reconfirmed

[Thomas Robitaille]

Hi everyone,

I occasionally come across old bug reports in astropy which end up having been resolved in the meantime due to refactoring, or can no longer be reproduced for whatever reason (for example the API may no longer exist or be relevant).

To help with triaging issues, I've taken the liberty of making a new 'needs-reconfirmation' label for issues and have applied it to any bug report which was opened before the end of 2021 - there are 113 such issues:

https://github.com/astropy/astropy/issues?q=is%3Aissue%20state%3Aopen%20label%3Aneeds-reconfirmation

I would encourage anyone who is interested in helping in taking a look and checking if the bugs still exist with the latest version of astropy. If the bug is confirmed to be still present, we can then remove the needs-reconfirmation label (if you are able to reconfirm but can't change the labels, just leave a comment).

Thanks!

Tom

[Kelle Cruz]

Great idea!  Would it be worthwhile to create a bot that adds a message to these issues, including a request for help?  That way, the original reporter will get a more substantial notification and call to action. 

Something like, "Thank you for reporting this bug! We have noticed that this issue has been open for quite some time and want to make sure that this bug still exists in the current version of Astropy (v7.1 or whatever). If possible, please let us know if this problem still exists or if it has been resolved and this issue can be closed. Thanks for your help in improving Astropy!"

I don't know how hard it is to make a bot to do this, but it seems worthwhile.

Kelle

--
You received this message because you are subscribed to the Google Groups "astropy-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to astropy-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/astropy-dev/CAGMHX_0vMpctZPfCEFZew5k5BouRjCRTZRkE6LpbGLX8HETfsw%40mail.gmail.com.