[opensuse-kde] Which bug reports go upstream?
In one of my latest bug reports Lubos Lunak said, "Please report problems with unstable versions upstream unless they're SUSE-specific." This was a report from the Factory, (KDE: 4.1.87 (KDE 4.1.87 (KDE 4.2 >= 20090101)) "release 78.4") which I thought was SUSE specific and not considered exactly UNSTABLE. If Factory is not considered SUSE specific then what is? Is it branding, packaging, patches, and backports only? I use KDE and openSUSE for work around ten hours every single day. I really only have time to report bugs to one location if I even manage to get around to reporting them. Should the beta-customer be deciding what reports go upstream from factory? It seems reasonable to me that all Factory reports should go to bugzilla.novell.com and that all UNSTABLE reports should go to bugs.kde.org. This way Factory can become SUSE specific due to the KDE Team deciding what goes upstream and what gets patched. -- Marc Benstein -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Am Donnerstag, 15. Januar 2009 18:45:38 schrieb Marc Benstein:
I use KDE and openSUSE for work around ten hours every single day. I really only have time to report bugs to one location if I even manage to get around to reporting them. Should the beta-customer be deciding what reports go upstream from factory? It seems reasonable to me that all Factory reports should go to bugzilla.novell.com and that all UNSTABLE reports should go to bugs.kde.org. This way Factory can become SUSE specific due to the KDE Team deciding what goes upstream and what gets patched.
That's easy. If the bug only occurs on opensuse, i.e. is due to packaging or because opensuse patched KDE, then you can report it at opensuse. If it is a KDE issue, i.e. valid no matter which distro you use, then it's upstream and you have to report it at KDE. This is especially true for unreleased, i.e. all versions except the one in STABLE and of course for unreleased apps like knetworkmanager4, k3b4 etc. 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. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
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. -- Marc Benstein -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
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@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
That's easy. If the bug only occurs on opensuse, i.e. is due to packaging or because opensuse patched KDE, then you can report it at opensuse. If it is a KDE issue, i.e. valid no matter which distro you use, then it's upstream and you have to report it at KDE.
so the little ......"gnome" at the corner of the screen puts up the sign telling us what sort of bug we just hit, no? or we can multi-boot to six other distros and look for the little gnome there? d. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Am Mittwoch, 4. Februar 2009 00:37:25 schrieb kanenas@hawaii.rr.com:
That's easy. If the bug only occurs on opensuse, i.e. is due to packaging or because opensuse patched KDE, then you can report it at opensuse. If it is a KDE issue, i.e. valid no matter which distro you use, then it's upstream and you have to report it at KDE.
so the little ......"gnome" at the corner of the screen puts up the sign telling us what sort of bug we just hit, no?
or we can multi-boot to six other distros and look for the little gnome there?
If others can test without causing a waste of time by filing upstream bugs at novell's bugzilla without sarcasm or six other distros, I'm sure you can too. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Thursday 15 of January 2009, Marc Benstein wrote:
In one of my latest bug reports Lubos Lunak said, "Please report problems with unstable versions upstream unless they're SUSE-specific."
This was a report from the Factory, (KDE: 4.1.87 (KDE 4.1.87 (KDE 4.2 >= 20090101)) "release 78.4") which I thought was SUSE specific and not considered exactly UNSTABLE.
KDE 4.1.87 is KDE4.2 Beta2 (?), an unstable KDE release. Factory is currently what will be in openSUSE11.2, in about half a year. Sven has already very well explained the rest.
If Factory is not considered SUSE specific then what is? Is it branding, packaging, patches, and backports only?
I use KDE and openSUSE for work around ten hours every single day. I really only have time to report bugs to one location if I even manage to get around to reporting them. Should the beta-customer be deciding what reports go upstream from factory? It seems reasonable to me that all Factory reports should go to bugzilla.novell.com and that all UNSTABLE reports should go to bugs.kde.org. This way Factory can become SUSE specific due to the KDE Team deciding what goes upstream and what gets patched.
The reason is actually about the same like yours. I don't know if you realize that although openSUSE is a community project and people help with bug screening and other things, a vast majority of KDE bugreports will have to be handled by only 3 people, who also have other things to do. That's how things are. People who definitely want to have better support need to pay for it, those who use openSUSE get it for free and that has some consequences. If every single bug in openSUSE KDE packages would go to our bugzilla first, we'd be completely overwhelmed and wouldn't be able to even cope with this one thing, let alone all the other things we need to do. Therefore we currently need to limit ourselves to our own bugs or bugs that are important. As I said, openSUSE is a community project, so if there would be enough people working on bugzilla screening, we could try more, but although current help from community members is a big help, we can take only so much, sorry. I understand you're trying to help, but keeping a bugreport for a bug in an unstable KDE release that will possibly be significant for openSUSE in only about half a year and will very likely be fixed by that time is very very low priority, so this needs some judgement on the feasibility. Imagine what would happen if everybody used our bugzilla the same way like http://bugzilla.novell.com/442933 . -- Lubos Lunak KDE developer -------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: l.lunak@suse.cz , l.lunak@kde.org Lihovarska 1060/12 tel: +420 284 028 972 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Fri, 16 Jan 2009 12:33:16 +0100, Lubos Lunak wrote
As I said, openSUSE is a community project, so if there would be enough people working on bugzilla screening, we could try more, but although current help from community members is a big help, we can take only so much, sorry.
So, my time helping openSUSE would be better spent screening bugzilla and sending the aforementioned bugs upstream. Unfortunately, I am never able to make the KDE meetings since my job does not permit. I do however read the transcripts and I am always looking for somewhere to fit in. Previously, it had been reporting bugs from Factory. But, I would like to help in a more efficient way since we are so far from the next release. Thanks for all the feedback. -- Marc Benstein -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Am Freitag, 16. Januar 2009 16:35:11 schrieb Marc Benstein:
So, my time helping openSUSE would be better spent screening bugzilla and sending the aforementioned bugs upstream. Unfortunately, I am never able to make the KDE meetings since my job does not permit. I do however read the transcripts and I am always looking for somewhere to fit in. Previously, it had been reporting bugs from Factory. But, I would like to help in a more efficient way since we are so far from the next release.
On http://en.opensuse.org/KDE#Bugs you can find links that give you a list of bugs reported. You can check them and if in doubt, ask the reporter for info or drop by #opensuse-kde on IRC. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
participants (4)
-
kanenas＠hawaii.rr.com -
Lubos Lunak -
Marc Benstein -
Sven Burmeister