Join us to show up for other Firefox users 🦊. Earn fun badges and Mozilla swag vouchers! Find out more: https://mzl.la/askafox150

Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Ways to improve testing quality of TB

  • 2 replies
  • 1 has this problem
  • 51 views
  • Last reply by rkent
  • Solved

I wonder, how could I possibly donate to improving TB new features/bug fixes testing? The story with

https://bugzilla.mozilla.org/show_bug.cgi?id=1036338

brought many unpleasant concerns. If bug of that scale could be left unnoticed until many angry comments started to flow in, there's room to improve QA of every fix/feature.

Personally, I can test daily builds. No problem doing that. Problem is, how to ensure that bug reports are taken into account? A single test on self-signed certificate, talking of the above bug, could indicate there's major problem with new release and perhaps postpone it till a remedy is found. Now, 2 months after the release, many users still have to use out-of-date versions, since no official report has been posted on whether the flaw will be attended to in foreseeable future.

I would like to use product (TB) knowing it's tested thoroughly, so that the cases like above could be avoided at all costs. What can I do for that, to know the results of my bug reports are indeed taken into account?

I wonder, how could I possibly donate to improving TB new features/bug fixes testing? The story with https://bugzilla.mozilla.org/show_bug.cgi?id=1036338 brought many unpleasant concerns. If bug of that scale could be left unnoticed until many angry comments started to flow in, there's room to improve QA of every fix/feature. Personally, I can test daily builds. No problem doing that. Problem is, how to ensure that bug reports are taken into account? A single test on self-signed certificate, talking of the above bug, could indicate there's major problem with new release and perhaps postpone it till a remedy is found. Now, 2 months after the release, many users still have to use out-of-date versions, since no official report has been posted on whether the flaw will be attended to in foreseeable future. I would like to use product (TB) knowing it's tested thoroughly, so that the cases like above could be avoided at all costs. What can I do for that, to know the results of my bug reports are indeed taken into account?

All Replies (2)

Chosen Solution

Thanks Konstantin for your willingness to look at the larger problem, and not just be angry about that one bug. I could talk with you for hours about the current issues in Thunderbird and what needs to be done, but my thoughts on the way forward are summarized in "Thunderbird Reorganization: Summary Plan" here:

https://groups.google.com/forum/#!topic/tb-planning/Uoz5DOsz_KY

In short, Thunderbird needs to re-organize to be self-governed by the community, and then needs to raise funds directly from users to pay for a few full-time developers.

The Thunderbird community will be assembling in Toronto for a critical meeting to discuss the future in mid October 2014, and hopefully a concrete way forward will come from that. It will be many months though until any changes can be put in place. Right now, what is most helpful is for you to follow any discussions on tb-planning, and add your perspective. Testing is always appreciated, and might have helped in this specific case, but as you also noted there are not enough developers available to address the issues at the moment, so any long-term solution must address that problem.