[opensuse] RE:How to get old bugs just look at and may be accepted - OTJust a little



In 2 separate discussions re Email clients I mention amongst some other
strong, but desperately apparent issues with bug reporting and actioning.

During the separate discussions I mentioned the number of outstanding
bugs and enhancements for Evolution that have been logged and not looked
at since 10.0.

Well it appears people take more notice of the mail list than running
reports in Bugzilla as I just got 14 bugs related solely on Evolution
opened for consideration in one email hit.

If you have a favourite application and have logged bugs and
enhancements the best way of getting them actioned seems to be asking
for help here on how to get around them.

Unfortunately with the disastrous incident with 10.2 Evolution and KDE
desktop, I had to change the company , and are very happy now with the
new direction and commitment to Thunderbird. I might even get time off
work and time off work at home to work one of my own new "extension"
and see how I go

I wont repeat the single harshly worded issue that concerned me, however
I will say I get very distressed when some one sends me a need info and
says "I don't believe you" - I just close the bug.

If I report in a bug a procedure that is 100% reproducible and then
someone sends me a needinfo for additional logs rather than perform 4
clicks for them self - I worry.

I must say that on the whole the guys at Novell.de and Mozilla are
really great and descent to deal with once they get to know you a little
and I cannot imagine the shear number of bugs KDE gets.


Good night
Scott :-P 21:12 GMT +10

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature



Relevant Pages

  • Re: 2.6.19 -mm merge plans
    ... I actually expected people to dislike arbitrary rules more than they do, but I've come to believe that people _like_ having rules that they have to obey, as long as it's not a big pain for them. ... So I think that a "odd release"/"even release" rule that clarifies what a certain mid-point in the release cycle actually _means_, even if it doesn't necessarily add anything else, might be a good thing. ... Then after people stop reporting show stoppers, change to rc numbers, where rc versions are actually candidates for release without known major bugs. ...
    (Linux-Kernel)
  • Re: Inheritance
    ... Go hooking to fix bugs in MS code? ... There's no site for reporting bugs in VS ... >> always be using the latest DDK. ... Maxim Shatskih, Windows DDK MVP ...
    (microsoft.public.development.device.drivers)
  • Re: First day with production development on D2005
    ... >> involved in reporting them vs. the benefit of reporting them. ... > The cost is taking some time to write the report. ... bugs are unlikely to get fixed and that show-stopper, ... not bother reporting bugs and if the development environment has too many ...
    (borland.public.delphi.non-technical)
  • Re: Wolfram Alpha claims to be a primary source.
    ... D> But your manner of reporting bugs, ... D> newsgroups in a dramatic way is not the best approach. ... It's probably not an unreasonable assumption that had Vladimir been professional about the way he reported bugs, he may well have been considered for employment by Maplesoft, Wolfram Research, perhaps Mathworks too. ...
    (sci.math.symbolic)
  • Re: Delphi 2007 more Flakey than 2006?
    ... I don't know how difficult this would be - as my bugs are all my own ... Windows has such a reporting system on board - called WER (Windows ... which attaches the stack trace similar to what Windows error ...
    (borland.public.delphi.non-technical)