RE: [opensuse] Bugzilla - a question
-----Ursprüngliche Nachricht----- Von: ianseeks Gesendet: So. 27.03.2016 14:08 An: opensuse@opensuse.org Betreff: [opensuse] Bugzilla - a question
Someone mentioned in the KDEPIM list that bugs can sit here "unnoticed" for years. Is there anyway of looking at a bug in bugzilla to check if any of the people assigned to look at it have actually read it other than them actually making a comment on it or changing the bug status?
Regards
Ian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----Ursprüngliche Nachricht Ende-----
Well, if you wish I can tell you. I am one of the reporters that got a bug closed after so may years that I received a letter of apologies for not having received any consideration before the change of generation took place. Bugs can stay there for about 3 years or longer. To know if your bug is looked upon, you should see if it has been "assigned" and at least if it has been "confirmed". If it is just confirmed but not assigned you have a "weapon", which is the vote. You can vote for a bug and some of the bugs that where unbelievably annoying to people, where fixed just because people did vote for it. We as a distribution may have noteworthy power if we put our forces together and get some bug fixed by popular vote if we do coordinate our votes. So I would say, if you have something that "stays on your heard" which is easy as with PIM as a central component, I think that KDE does still not understand the paramount importance for daily usage that this component has, and you may try to argue for a bug here, I for sure would be available to vote in a coordinated matter when it comes for PIM bugs. Others (I think of Anton and Basil :-p) may do so, driven by an act of profound altruism. You let me know what you need, and if I have votes to spare you will get my support. I firmly believe that one of the mayor problems of this otherwise very enjoyable desktop is priority setting. PIM and Kmail (filtering, akonadi etc) are part of it. Bear in mind however that (for what I heard) they are working on a complete rewrite of PIM/Akonadi to drive out design errors and bugs. So if the problems you face will be fixed through this, i am afraid, chances are good that this will be "wontfix" if the devs think it will be obsoleted by the new version anyway. (Which, to tell the truth, I hope so, it is time to get this very central component working and shining, if not other to heighten the reputation of the software collection as a whole). --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! https://email.freenet.de/mail/Uebersicht?epid=e9900000451 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sunday, 27 March 2016 15:44:09 BST stakanov@freenet.de wrote:
-----Ursprüngliche Nachricht----- Von: ianseeks Gesendet: So. 27.03.2016 14:08 An: opensuse@opensuse.org Betreff: [opensuse] Bugzilla - a question
Someone mentioned in the KDEPIM list that bugs can sit here "unnoticed" for years. Is there anyway of looking at a bug in bugzilla to check if any of the people assigned to look at it have actually read it other than them actually making a comment on it or changing the bug status?
Regards
Ian
-----Ursprüngliche Nachricht Ende-----
Well, if you wish I can tell you. I am one of the reporters that got a bug closed after so may years that I received a letter of apologies for not having received any consideration before the change of generation took place. Bugs can stay there for about 3 years or longer. To know if your bug is looked upon, you should see if it has been "assigned" and at least if it has been "confirmed". If it is just confirmed but not assigned you have a "weapon", which is the vote. You can vote for a bug and some of the bugs that where unbelievably annoying to people, where fixed just because people did vote for it. We as a distribution may have noteworthy power if we put our forces together and get some bug fixed by popular vote if we do coordinate our votes. So I would say, if you have something that "stays on your heard" which is easy as with PIM as a central component, I think that KDE does still not understand the paramount importance for daily usage that this component has, and you may try to argue for a bug here, I for sure would be available to vote in a coordinated matter when it comes for PIM bugs. Others (I think of Anton and Basil :-p) may do so, driven by an act of profound altruism. You let me know what you need, and if I have votes to spare you will get my support.
I firmly believe that one of the mayor problems of this otherwise very enjoyable desktop is priority setting. PIM and Kmail (filtering, akonadi etc) are part of it. Bear in mind however that (for what I heard) they are working on a complete rewrite of PIM/Akonadi to drive out design errors and bugs. So if the problems you face will be fixed through this, i am afraid, chances are good that this will be "wontfix" if the devs think it will be obsoleted by the new version anyway. (Which, to tell the truth, I hope so, it is time to get this very central component working and shining, if not other to heighten the reputation of the software collection as a whole).
Thanks. It was just a general question at the moment. I was interested in finding out if it was possible to find out if the long standing bugs were "unseen" or "seen" without any status being changed. I've had a few bugs in the system but i seem to close most them as i move onto newer releases of that software.
--- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! https://email.freenet.de/mail/Uebersicht?epid=e9900000451
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/27/2016 09:34 AM, ianseeks wrote:
I was interested in finding out if it was possible to find out if the long standing bugs were "unseen" or "seen" without any status being changed.
If you have a bug found in one release, it will be ignored as a subsequent release is produced, UNLESS you go back, test it again, and update the bug report to report it still has the problem. Basically, if you don't care enough to revisit the bug, they won't care enough to even look at it. I recently was able to shame the Baloo developers into fixing a hack they put in the file extraction routine back in 2014 which prevented the indexing of plain text files unless the extension was .txt. This pretty well eliminated the usefulness of Baloo, because tons of stuff evalutates as plain/text but does not have an extension of .txt. I had to find the exact line in the program that caused this error, and I updated the bug report with every single point release of baloo pointing out that the bug still existed. This went on for a long time before someone noticed. Of course their eventual fix still hasn't made it to Opensuse update Repositories, which is yet another problem. And on any major release, such as moving to Plasma from KDE4, ALL bugs are considered closed, but simply abandoned in the open state. The various bugzillas really do need an Auto-Closed-pending-Reopen status, imposed by some daemon, or triggered by a new release, Which would at least notify the submitter(s) that the bug needs to be re-opened by the original submitter(s) after they verify it still exists. When so many developers are simply volunteers, (and young ones at that), its hard to impose any sense of responsibility, or even pride in workmanship. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday, 28 March 2016 10:56:35 BST John Andersen wrote:
On 03/27/2016 09:34 AM, ianseeks wrote:
I was interested in finding out if it was possible to find out if the long standing bugs were "unseen" or "seen" without any status being changed.
If you have a bug found in one release, it will be ignored as a subsequent release is produced, UNLESS you go back, test it again, and update the bug report to report it still has the problem. Basically, if you don't care enough to revisit the bug, they won't care enough to even look at it.
Yes, thats what i tend to do but probably not as timely as i should. Thats why I think it would be good if bugzilla could, in some way, flag up that a bug has been "looked" at (i.e. Just viewed but not updated in any way) so the bug submitter can see that its been noticed.
I recently was able to shame the Baloo developers into fixing a hack they put in the file extraction routine back in 2014 which prevented the indexing of plain text files unless the extension was .txt. This pretty well eliminated the usefulness of Baloo, because tons of stuff evalutates as plain/text but does not have an extension of .txt.
I had to find the exact line in the program that caused this error, and I updated the bug report with every single point release of baloo pointing out that the bug still existed. This went on for a long time before someone noticed.
Of course their eventual fix still hasn't made it to Opensuse update Repositories, which is yet another problem.
And on any major release, such as moving to Plasma from KDE4, ALL bugs are considered closed, but simply abandoned in the open state.
I didn't know that but i was thinking it might be the case.
The various bugzillas really do need an Auto-Closed-pending-Reopen status, imposed by some daemon, or triggered by a new release, Which would at least notify the submitter(s) that the bug needs to be re-opened by the original submitter(s) after they verify it still exists. Even a reminder to the bug submitter to have another look at it.
When so many developers are simply volunteers, (and young ones at that), its hard to impose any sense of responsibility, or even pride in workmanship. They must be swamped with reports as well and i guess "scratching the itch" is more fun developing new stuff. I have found the team developing Plasma 5 quite good on chasing bugs.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/27/2016 06:44 AM, stakanov@freenet.de wrote:
KDE does still not understand the paramount importance for daily usage that this component has,
That's because nobody is using KDEPIM, because it is in such a state of shambles. It seems like Everybody has moved on to other solutions, some of them paid, some of them free, because the interoperability and reliability of KDEPIM, and the amount of memory that Akonodi requires makes them uniquely unsuited for any purpose that requires them. For years on end, the calendar plugins didn't work. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
ianseeks
-
John Andersen
-
stakanov@freenet.de