On Mon, 2008-10-06 at 22:48 +0200, Marcus Meissner wrote:
On Mon, Oct 06, 2008 at 10:20:29PM +0200, Hans-Peter Holler wrote:
Sorry I were too late: Marcus, you said: Sorry, but such things can happen more often since we develop openSUSE 11.1 and SLE 11 in parallel.
And this is what I wanted to say:
I _do_ this with posting on top:
"You are not authorized to access bug #431542."
I am an authorized member to the public bugzilla and I know that especially SLE-bugs meeting openSUSE-bugs are marked as private/internal. So, if the person assigned to the internal bug is not aware of the public dependency, that could be be explained twice: - That person is too dumb to read all dependend bug reports (no no no) - Novell's/SUSE's SLE-policy says: yes to all coming in from the outside, but don't let anything come out
And I know this reads angry: I _am_ angry with this!
The bugzilla is used for openSUSE, SUSE Linux Enterprise, and lots of Novell products. It is only open for the public for openSUSE.
There is no internal bugzilla, there is just this one, bugzilla.novell.com.
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.
Ciao, Marcus
Cheers, Magnus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org