I was told about arch linux about how you could click a button to 'flag' a package for updating ie notifying the maintainer that the package needs to be updated. Many bugs in the tracker are added and include a simple "rename the ebuild" users often not contributing the ebuild because in a lot of cases it's unnecessary especially when it only involves having the version number altered, or they might not know what to change. I'm thinking of a system where, you login with your bugzilla account and if a package is out of date in the tree with portage tree you click the button, and it makes a bug in the tracker automatically adding the name of the package ie "catagory/package - Version Bump" and the URL fields. Also it could automatically assign to the necessary team/maintainer. If the button has been pressed by someone it greys out until a developer commits the ebuild and "unlocks it." This way it would prevent duplicate bugs in the tracker and stop our bugzilla assigners from assigning duplicate bugs for 0day requests etc on packages. Might me more trouble than it's worth, I mentioned it in the #gentoo-bugzilla channel and they said to file it here under the bugzilla section. (Note this is only a basic outline, I have not thought about all the possible problems of such a system/methods etc.) Reproducible: Always Steps to Reproduce:
Patches welcome, look up the gpackages codebase. http://sources.gentoo.org/gitweb/?p=packages.git;a=summary I think the quickest way would be to not care about existing bugs, but have a link using the saved template system, next to each existing bugzilla link, for users to open a new bug, nicely titled with the CAT/PN already.
Moving to component for new site. I think it's useful, but needs very careful UI design to avoid filing INVALID bugs. On TODO for new site.
