Mailinglist Archive: opensuse-kde (180 mails)

< Previous Next >
Re: [opensuse-kde] Which bug reports go upstream?
  • From: Sven Burmeister <sven.burmeister@xxxxxxx>
  • Date: Thu, 15 Jan 2009 19:42:22 +0100
  • Message-id: <200901151942.22951.sven.burmeister@xxxxxxx>
Am Thursday 15 January 2009 19:24:13 schrieben Sie:
On Thu, 15 Jan 2009 19:05:52 +0100, Sven Burmeister wrote

For the packages in stable it does make sense to report to bugzilla,
because the patches to STABLE will be published as YOU update later
on. The latter however only applies to bugs, not feature requests,
since STABLE will not get any new features.

So it is more beneficial to openSUSE if KDE users test STABLE, instead of
Factory or UNSTABLE.

STABLE is important, Factory becomes more important the closer they get to a
new openSUSE release. UNSTABLE is completely useless for them, since it is
neither part of any released openSUSE version, nor being worked on for a
future release.

With their limited resources they have to focus on STABLE and openSUSE-
specific bugs/features. Further, they cannot be experts for every single
application, so the maintainer of that application at bugs.kde.org is likely
to have more knowledge and can fix things quicker.

Every non-openSUSE-specific bug, should have a report at bugs.kde.org. If it
is a really important feature, like e.g. bluetooth support not working at all,
or a really importand bug, which might already be fixed upstream (can't think
of any ATM), then it does make sense to file it downstream too and add the
upstream bug report into the URL field. That way they can keep track of
showstoppers before a release and crucial fixes after a release.

Sven
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-kde+help@xxxxxxxxxxxx

< Previous Next >