Bug#526779: Forwarding bugs upstream (Was: Bug#526779: battery-applet: Misleads about still charging)
Sheridan Hutchinson wrote: In my view, what you have wrote is completely contrary to the spirit and the wording of section 3.5 of the Debian Developer's Reference: http://www.debian.org/doc/manuals/developers-reference/developer-duties.html#upstream-coordination I refer specifically to this sentence: A big part of your job as Debian maintainer will be to stay in contact with the upstream developers. Debian users will sometimes report bugs that are not specific to Debian to our bug tracking system. You have to forward these bug reports to the upstream developers so that they can be fixed in a future upstream release. With this wording it would appear that the onus does fall on KDE developers to forward this to upstream. I invite your comments. So you have found the Developer's Reference. Nice. The problem is, that we have no way to realize what is written there. We simply have not the manpower to forward the tons of upstream bugs we receive. KDE is a very very huge beast and we are very less developers. Sou our choices are to a) Package new releases and fix packaging bugs, or b) Forward bugs upstreams. So, what do you prefer? It is not that we are to lazy to forward the bugs, we would love to do it. But sadly it is not possible. I find it way less rude to tell you that it is not likely that we forward the bug upstream instead of letting the bug rot the next 3 years and then as you to report if the bug still applies. I hope you get the point. Everyone is welcome to join the team and forward bugs btw... Greetings, Armin -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526779: Forwarding bugs upstream (Was: Bug#526779: battery-applet: Misleads about still charging)
Hi Armin, Thanks for your reply. I take on board that there can only be so much manpower available in the team. I'll make sure I'll send KDE bug reports just upstream in the future. -- Regards, Sheridan Hutchinson sheri...@shezza.org -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526779: Forwarding bugs upstream (Was: Bug#526779: battery-applet: Misleads about still charging)
Hello, On 2009 m. May 29 d., Friday 20:47:23 Armin Berres wrote: I refer specifically to this sentence: A big part of your job as Debian maintainer will be to stay in contact with the upstream developers. Debian users will sometimes report bugs that are not specific to Debian to our bug tracking system. You have to forward these bug reports to the upstream developers so that they can be fixed in a future upstream release. With this wording it would appear that the onus does fall on KDE developers to forward this to upstream. I invite your comments. I find it way less rude to tell you that it is not likely that we forward the bug upstream instead of letting the bug rot the next 3 years and then as you to report if the bug still applies. In fact, the let upstream bugs rot for years practise has already been in effect for *years*. We changed it a bit to let users know about it so they can do something to get their bugs actually solved. I think it is better because: 1) The user knows that probably no real action is going to be taken on his/her Debian bug. Moreover, clear instructions in the mail help the user to get the bug actually solved (given upstream cares about the bug). 2) The user knows that debian kde developers think the bug is KDE (upstream) bug, not packaging bug. 3) We are still commited to solving packaging bugs or help solving grave/serious/critical upstream bugs. Clear separation of those two kinds means the bugs that we CAN solve do not get lost among the bugs we CANNOT solve. Regardless what manuals say, you can follow them 100% only if your package is small. But KDE is HUUUGE with lots of packages. In that case you have to change common practise to meet the reality of the real world. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Bug#526779: Forwarding Bugs upstream (was: Bug#526779: battery-applet: Misleads about still charging)
On Fri, 29 May 09 07:36, Sheridan Hutchinson wrote: In my view, what you have wrote is completely contrary to the spirit and the wording of section 3.5 of the Debian Developer's Reference: http://www.debian.org/doc/manuals/developers-reference/developer-duties.html#upstream-coordination I refer specifically to this sentence: A big part of your job as Debian maintainer will be to stay in contact with the upstream developers. Debian users will sometimes report bugs that are not specific to Debian to our bug tracking system. You have to forward these bug reports to the upstream developers so that they can be fixed in a future upstream release. With this wording it would appear that the onus does fall on KDE developers to forward this to upstream. I invite your comments. So you have found the Developer's Reference. Nice. The problem is, that we have no way to realize what is written there. We simply have not the manpower to forward the tons of upstream bugs we receive. KDE is a very very huge beast and we are very less developers. Sou our choices are to a) Package new releases and fix packaging bugs, or b) Forward bugs upstreams. So, what do you prefer? It is not that we are to lazy to forward the bugs, we would love to do it. But sadly it is not possible. I find it way less rude to tell you that it is not likely that we forward the bug upstream instead of letting the bug rot the next 3 years and then as you to report if the bug still applies. I hope you get the point. Everyone is welcome to join the team and forward bugs btw... Greetings, Armin -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
