Hello,
Am Montag, 20. Februar 2006 14:07 schrieb Karl Eichwalder:
> Eberhard Moenkeberg <[EMAIL PROTECTED]> writes:
> > I don't think they are part of "ClosedSUSE", I hope they are only
> > entered by individual idiots (there is a slight difference between
> > "individual" and "idiot", but only in newer ages)...
>
> Let's blame the system. You start testing SLES and classify defects
> as SLES issues. That's probably a fair assumption. Now the assignee
> (or someone with sufficient rights) must check whether the issue also
> affects SL and change the product accordingly.
If I got it right, SLES and SL currently use the same codebase. So you
can assume that nearly _every_ SLES bug is also a SL bug. (At least as
long as it doesn't concern SLES-exclusive features...)
> If no one bothers, the report stays closed.
How can one bother if he can't access the bugreport?
That's a chicken-egg-problem ;-)
I'd like to make the following proposal:
- as soon as a report for SLES gets a duplication message from another
bugreport for SL, move it to SL - it is REALLY annoying if people see
"this bug is a duplicate of #xxxxx", but can't access #xxxxx and
therefore can't watch the bug.
- if a bug is listed at the "Most Annoying Bugs" page, open it - listing
it on opensuse.org qualifies it as SL bug also ;-)
Or simply:
- open all SLES 10 bugs :-)
Maybe this should be discussed on the overnext status meeting (in 2
weeks) to give you a chance for finding a reasonable solution.
Or already tomorrow [1] - just ask the participants what they would like
to have.
Regards,
Christian Boltz
[1] unfortunately, I won't be able to take part at the IRC meeting
tomorrow :-( but I will check the transcript.
--
> :digraphs und :h digraphs
> *ŠÇÑ®*
Wenn man dann nur noch so unleserlich schreiben kann, bleibe ich lieber
bei KMail ;) [> Maik Holtkamp und Manfred Misch in suse-linux]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
