Am 16.04.20 um 00:06 schrieb Christian Boltz:
The answer was always that "the problem is understood, it isn't easy to fix, and it will be evaluated and improved". I'm sorry to say that, but I've heard this long and often enough, and will only believe you once I see lots of public SLE bugreports ;-)
#Metoo
(Just wondering - Simon, how many bugshare requests do you/the bugshare team receive per month)
I'd guess a very low number, because what you get in return is not useful at all (at least for my requests, it was not really useful).
Getting a rough summary of a bugreport isn't too helpful,
Applause for putting this into such nice, friendly words.
IIRC bugshare was meant as a quick-to-implement workaround until we get the real problem fixed - but I haven't seen progress on the "make (most) SLE bugs public" topic since then.
Probably about as much progress as on the "abandon connect.o.o" front ;-)
In the meantime, I stopped trying bugshare after getting some not-too- useful summaries and sometimes not always getting an answer at all. Instead, I switched to reading the added patches when seeing a non- public boo/bsc number in a changelog. That's faster (no need to wait/ hope for a bugshare reply) and more helpful - the patch shows what was done, and often allows to understand the underlying bug better than a rough summary of the bugreport. Sadly, this "reverse engeneering" method takes much more time than reading a bugreport, and requires at least some basic knownledge of coding and reading patches.
I'm doing exactly the same, but pardon me -- this is not worthy of an "open" SUSE operating system.
As you can imagine, though, the devil is in the detail, as in many cases, bugs are filed on behalf of customers or partners, where SUSE needs to protect customer/partner specific information.
But you are aware of that challenge anyways, aren't you?
Yes, I'm aware of these challenges - I've heard about them often enough ;-)
Me too. Heck, I even file as many of our SLES bugs as possible against FACTORY / Leap (often complete with patches and fixes...), just to keep them accessible for everyone. And then they are moved to SLES in the bugfixing process 🤦 This is somewhat insulting...
And yes, there might also be some bugs that have to be completely non- public (for example security issues[2] or bugs discussing things that are under NDA). That's completely understandable, and as long as this is only the minority of bugs, it's not a serious problem.
Fun fact: I have not yet encountered a security bug mentioned in a Leap changelog that was not accessible. The security team is doing their homework very well.
[2] actually the security team is quite good at making bugs public once the fix is released and the embargo is lifted
Aah, should have read the footnotes first ;-) -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org