SeaMonkey Internet Suite

Unofficial News in English language


Leave a comment

Bug 1329724 – Empty lines in email body disappear

Zur Mozilla-Bugzilla HomepageBased on postings in de.comm.software.mozilla.mailnews (“[SM 2.46] Leerzeilen verschwinden beim Antworten”) I reported Bug 1329724 – Empty lines in email body disappear, but until now it seems nobody was able to reproduce the problem with the steps from bug report.

I did tests on mozilla.test with Server-Installations of unofficial (by FRG) en-US SeaMonkey 2.50a1 (NT 6.1; Win64; x64; rv:53.0) Gecko/20100101 Firefox/53.0 Build 20170108183322 (Default Classic Theme) on German WIN7 64bit (Re: Empty lines disappear, Rainer Bielefeld 06:08 +0100, Message-ID: <V8OdnYbIGKeq8enFnZ2dnUU7-cOdnZ2d@mozilla.org>, and the issue was still reproducible.

It would be great if someone else could reproduce the problem with the Steps To Reproduce from my report.

And, of course, it also would be great if you find other reliable ways how to provoke disappearing empty lines in replies; please submit additional separate Bugs if you are not sure that the problem you observe is exactly the same.


Leave a comment

Mac is back (new official Trunk builds)

This blog post in German languageAfter a while of waiting we now have new SeaMonkey Trunk  builds for MAC

Be careful! These builds are for testing purposes only. Keep backups of your data, some of the code you’re testing might not have been tested at all before and might cause unexpected problems. If you encounter any such problems, please report bugs for them.

Continue reading


Leave a comment

My UNCONFIRMED Bug Reports

Zur Mozilla-Bugzilla Homepage I still report new bugs I find with status UNCONFIRMED, even if (after careful investigation) I am pretty sure that the report is concerning a real bug and complete enough so that a developer can take on. Reason is that I believe in the two-man rule. Often a review by an other user adds information, may be concerning additionally affected Operating System or an aspect of the problem not yet mentioned or something else. But in the SeaMonkey project, due to very limit “human QA resources” and the lack of interest of most SeaMonkey users to contribute to the project, the bug review process  is horrible slow, even Bug reports what can be reproduced easily do not find a user who is willing to do a test whether he can reproduce the problem.

SeaMonkey needs you

So in future I myself will change bug status to NEW after 2 weeks (or so) of waiting if I think that all requirements for starting bug fixing process are fulfilled and nobody confirmed the bug. But, of course, it would be great if YOUR help would make superfluous this proceeding with my own “confirmation”. Be courageous and grasp the nettle of confirming some [easyconfirm] bugs.


1 Comment

Latest Developer builds

This blog post in German languageCorrected contents from unmaintained pages from seamonkey-project.org (2016-06-27)

Be careful! These builds are for testing purposes only. Keep backups of your data if you do so, as some of the code you’re testing might not have been tested at all before and might cause unexpected problems. If you encounter any such problems, please report bugs for them.

Continue reading


1 Comment

QA: New Whiteboard-Tag “[easyconfirm]”

Zur Mozilla-Bugzilla HomepageThis blog post in German languageSome time ago I introduced the Bugzilla-Whiteboard-Tag “[easyconfirm]” for the SeaMonkey-Project. This tag is for UNCONFIRMED  SeaMonkey-Bugs  which can be reproduced and confirmed easily even by beginners.So these bugs are suitable for first steps in our Bug-Tracking-System.

It would be great if SeaMonkey-users, which have not been working actively in the project until now, would use the opportunity to become familiar with SeaMonkey QA. A very good collection of big-triage – how-tos you can find here. Also the Bug Writing Guidelines contain useful hints. It is not necessary that you learn all that stuff by heart before you start, simply scan through and then start with “learning by doing”.

I hope to meet you soon in Bugzilla, click the [easyconfirm]-link above and try to reproduce and confirm your first bug.