Internal Server Error
If you just found a SeaMonkey bug, you will have to be patient: Bugzilla is not (reliably) available from 17:00 UTC until 20:00 UTC (estimated).
Internal Server Error
If you just found a SeaMonkey bug, you will have to be patient: Bugzilla is not (reliably) available from 17:00 UTC until 20:00 UTC (estimated).
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.
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.
(Currently Linux only as a first step, copy from download repository)
Only for testing, you will use those builds on your own risk. I recommend to create a backup of your user profile before you start testing those builds.