-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2008-10-07 at 07:58 +0800, Magnus Boman wrote:
But yes, our packagers should be more careful not to cut you off.
The issue, for developers, is that they have an existing bug report where issue XYZ was reported. He then gets assigned another one where XYZ happend, which is a duplicate. So what does he do? Obviously, marks the second XYZ bug as a dupe of the first one. Unless something in bugzilla can then warn the developer that he's marking a public bug duplicate of an "internal" bug, these things will happen. I mean, we can't expect the developer to keep track of all his bugs and from what product the came from, especially since they most often have more than enough bug reports to keep them busy fixing issues. Adding an extra overhead of trying to manually administrate this is, in my opinion, wrong.
I don't know how bugzilla works internally, but I assume it has a database, and that you can add triggers or code to be executed when certain actions happens, like "if status=close and reason=dupplicate, then run check". Such a code could check for this situation, I suppose. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjql7AACgkQtTMYHG2NR9We3gCfbw15OR/75C32p3IoYH0tMweD PmgAoJAzSEOZBRUBHr2uTGCZJVPgRqji =MkiX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org