[gentoo-dev] on closing bugs.

[George Shapovalov]

Hi gang

Looks like recent Daniel's announcement prompted flurry of bug-closing 
activity, which is good of itself, however there are some particulars :).

For example recent bugzilla changes left me with a long list of reopened bugs, 
which should basically all be closed. However this is an excellent 
opportunity to go over these packages (and it appears that over time I 
processed quite a bunch of stuff, not always directly related to the herds I 
am officially in now, and which doesn't seem to have been picked up in late 
reorganization so far) and check them for updates and the like, on which I 
would rather not pass up. Thus here goes my plea:

If you see the bug that looks like it should have been closed long since, you 
may close it if you so wish, but *please do the update checks* first, or 
leave them to me ;) (but I am certainly not against help, that is if it is 
done properly ;)). Pretty much all these packages are low maintaince and 
belong to "weird" areas (thus users are slow on pointing out an 
outdatedness), so there should not be much work involved ;).

Just to be completely clear: it is perfectly fine to [re-]close the dups and 
bugs for which there is one (a bug, not a package in tree, since there might 
be even more recent one on the developer's site) for a newer version. I would 
just like to ask for a bit more attention on the non-duplicated bugs..

Thanks!

George



--
gentoo-dev@g.o mailing list