« Help find leaks in SeaMonkey | Main | Need testing for SeaMonkey 1.0.1 »
January 25, 2006
Need testing of SeaMonkey 1.0 release candidate
We've fixed the blockers we needed to fix for SeaMonkey 1.0 and have builds ready for testing (except for gtk1, which we should have later today). If we don't find any major regressions, they will become the release builds. Please download a build and make sure it works for all the common tasks you use it for. If you encounter a problem, file a bug. If you think it should block the release of SeaMonkey 1.0, nominate it with the blocking-seamonkey1.0 flag.
We also need people to run sometests using Testrunner before release. Please stop by #seamonkey if you'd like to run the smoketests.
Update: be sure to grab the "1.0" builds from the ftp directory and not the older "1.0b" builds.
Posted by ajschult at January 25, 2006 10:34 AM
Comments
After nearly 9 hours of regular use (on and off), I've not noticed any problems. Extensions and themes are working fine, Mail/Newsgroups, no problems. Very PLEASED, I am. Excellent so far!
Posted by: Uncle Spellbinder at January 26, 2006 5:19 PM
Good to see SeaMonkey reaching Release Candidate status! :)
Posted by: Pu7o at January 27, 2006 12:56 PM
I just thought I'd give this new Seamonkey a go, after having used Opera (and occasionally Firefox) for a long time.
In only minutes, I'm really surprised by a couple of things:
1) It insists on placing icons on my desktop and in the quicklaunch bar.
2) When opening, not only the Personal bar is opened by default, but also the sidebar. This sort of UI clutter has been abandoned by Firefox and Opera a long time ago.
3) To add insult to injury, both the removed Personal bar *and* sidebar keep appearing at every startup. I'm really not going to remove them manually every time I start the browser, so this alone is enough to stop using it. (This may have something to do with the Profile Hell I always experience when using any Mozilla based product.)
4) Newly installed themes don't appear in the View -> Apply themes menu. You have to restart the browser first, choose the theme and restart it *again* to apply.
5) When entering a URL for the first time, the top 2 pixels of the (empty) dropdown menu appear right under the URL field.
6) The splash screen and the throbber make use of the new Seamonkey icon, but the taskbar and the Alt+tab switcher use the old Mozilla icon...
Really, all Mozilla based browsers are built on a solid basis where standards support is concerned, please spend some time on refining the user interface some more before shipping this.
Posted by: Fabian at January 29, 2006 4:29 AM
Fabian,
#1 has a bug already on file.
#2 and #3 is a bug that probably depends somehow on your profile.
My first shot at theme installation didn't work at all, but a second theme installed properly and showed up immediately in Apply Themes.
Could #5 be because you were using a 3rd-party theme?
Posted by: Andrew Schultz at January 29, 2006 9:45 AM
Thanks for the feedback, Andrew.
After creating a blank profile, my problems 2, 3 and 5 are gone. Still, this is one of the main weaknesses of Mozilla IMHO. Normal users shouldn't have to take care of incompatible profiles if they happen to have had Mozilla or Firefox installed earlier (and that's quite likely). Chances are they'd never know how to solve these sort of things.
For the rest: thumbs up!
Posted by: Fabian at January 29, 2006 1:25 PM
Fabian, if you still have your old profile and can identify what part of your profile caused #2 and #3 (I'm assuming #5 was from the theme, which we can't help) it's likely we could fix it for our next release (1.1). Not filing bugs for annoying problems is an excellent way to see them again in future releases.
Posted by: Andrew Schultz at January 30, 2006 10:28 PM