On Sun, Aug 19, 2007 at 03:13:50PM -0700, Roland McGrath wrote: > Does bodhi always automatically close the bugzilla bugs whose #s you list > in the update? The old updates system (for FC-6) has a checkbox for this. Bodhi now has this checkbox as well[0]. I will be updating the production instance hopefully this week. > This seems like a bad thing. I like to list the related #s, while a) > sometimes giving reporters a chance to verify before closing them and b) > listing some that were reported against fc6 or devel in the f7 update and > vice versa. This is for updates where devel, F-<n>, and F-<n-1> are all > getting the same rpm modulo %dist at the same time. It's anal overkill to > clone each bug for each other version, and I'm not going to do it. It's > just unfriendly to the users to omit the bug # from the update just because > it's a bug only reported for a different Fedora release, so I don't want to > do that either. It's not the end of the world for fc6 and devel bugs to > get closed by a robot saying "this here F-7 update fixed it", but it's not > really what I as the maintainer this robot serves want it doing in my name. Agreed. So, right now in the current production instance, bodhi comments on bugs when an update is pushed to updates-testing. When it is moved to Stable, then it will close them all. As I mentioned above, this will be completely optional soon. > I didn't file this at https://hosted.fedoraproject.org/projects/bodhi/newticket > because "TICKET_CREATE privileges are required to perform this operation". Did you login first ? luke [0]: https://hosted.fedoraproject.org/projects/bodhi/attachment/wiki/Screenshots/bodhi-new.png -- Fedora-maintainers mailing list Fedora-maintainers@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers -- Fedora-maintainers-readonly mailing list Fedora-maintainers-readonly@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
