First, Thanks to those who replied. I really appreciate it.
I'd say if you know that they are fixed you should just close them explaining that. If there's some issue and the maintainer(s) want them to stay open they can always re-open them.
To me, this seems a little pushy and I wouldn't feel comfortable doing that.
IMHO, you can always ask also in the bug: "Should this be closed? I think it's fixed and will close it in 1 week unless I hear otherwise"
Now this seems just perfect for me. I think I will go back to the bugs I sent the e'mails on and do this.
Personal email about bugs has lots of issues too: * What if the maintainer(s) you mail are no longer taking care of the package and just drop your emails, but then someone new takes over the package. That new person(s) would see all the existing bugs, but would have 0 idea of what your emails might have said to the old maintainers. * Are you sending to just the point of contact? Or to all maintainers/co-maintainers? Perhaps some co-maintainer is the active person and the point of contact you send to could care less. * Perhaps some provenpackager sees your bug and fixes it. They can tell you/update the bug, but if you send email to maintainers, they would have no idea it even happened.
Point well made. I hadn't covered all the bases. With a note as above anyone can see what happened. I won't be doing the e'mail method anymore.
Have a Great Day! Pat (tablepc) _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
