![]() ![]() So IF one wants UPSTEAM to fix this, then by working with him on a problem, one IS in fact also working UPSTREAM (although he is wearing a SuSE-GmbH 'hat' at the time he solves such bug reports, and accordingly he submits the fixes 'upstream 'to follow the Linux process, where the UPSTREAM submission is mostly a process formality/tracking process - because he IS upstream). I do note in the case of sound, that the SuSE-GmbH sound packager, who was handling the bug report you refer to, is one of the main UPSTREAM developers of alsa driver. I would have tried a new package if he said so.The marking of bug reports as 'FIXED' or 'RESOLVED' when the problem is upstream appears to be a SuSE-GmbH management policy, that the packagers follow. He doesn't require it, it is buggy upstream.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |