I notice they're using the May 31st 1.0-branch build as 1.0 . I'm on the 2nd of June 1.0-branch build right now.
Maybe they decided to junk several days' work due to mistakes.
Actually, we're already moving forward to Mozilla 1.0.1:-)
I want to personally thank everyone that downloaded Milestone and nightly testing builds and contributed feedback in the form of Bugzilla bug reports, TalkBack crash reports, comments in the newsgroups and at mozillaZine.org. And a special thanks to those people that gave a hours, weeks, months or years of their lives to the care and feeding of our bug database (triage and testcasing bug reports). Without Mozilla's amazing QA and testing community we wouldn't be where we are today. Oh, and all the developers too;-)
AOL embeds a rendering engine in it's application. There are very few Mozilla usability issues in any embedded context since the majority of the UI is not Mozilla but rather the embedding application. Right now AOL embeds a microsoft rendering engine in its AOL 7 client and a Mozilla rendering engine in its Compuserve cleint. Users shouldn't notice the difference between the microsoft and Mozilla rendering engines. Your usability arguement doesn't make a lot of sense in the embedded context (with the exception of web applications and other "in content" usability issues).
This was the perfect earthquake for an earthquake virgin like me. It was just strong enough to know that it wasn't my imagination but not so strong that anyone got hurt or any property got damaged. I'm in Redwood City, CA and it was a thrilling experience.
If you look at what actually happened this feature was removed for 1.0, not for the 1.1. And if you look even closer you will see that it wasn't disabled because of 1 bug. It was disabled because of performance problems and incompatability with tabbed browsing.
Because the page that comes up comes up for all previous builds. They all suffer (except RC1) and it was easier this way.
--Asa
Re:please!!! produce an unstripped linux nightly
on
Mozilla 1.0 RC2 is out
·
· Score: 4, Informative
There are talkback nightly builds for linux. If you can reproduce a crash consistently then file a bug. You don't have to have a stack if you can repro regularly. If it's reproducible then someone else can get the stack.
This doesn't fix a security hole from RC1. RC1 didn't have that security hole (it was obscured by the entire feature not working). Mozilla 0.9.9 did have the hole and it's now fixed in RC2. But this is not a security release. This release didn't happen because of the security fix (you could get that in a nightly builds many many days ago). This was a planned release based on feedback from RC1. We fixed 270 bugs between RC1 and RC2 including the most frequently encountered crash and hang problems.
Did you install on top of a previous install? If you did then remove that install and start fresh (you won't lose your profile, it's stored in a different location).
--Asa
The Mozilla 1.0 branch is planned as a long-lived stability branch with minimal or no new features. Folks looking for a stable and slower-moving codebase on which to build other applications should have an easier time tracking the 1.0 branch than the fast and furius trunk which will be taking features and other destabilizing changes on the road to Mozilla 2.0.
Bugzilla is not the place for an "ordinary customer". Bugzilla is a bug database, not a support forum. Ordinary customers need support and should use browsers, like Netscape 6.2, that offer support. Mozilla makes binaries available for testing and it is testers and developers for which our bug tracking tool is designed.
A better question might be "Why is there a big spike up for all of the platforms over the last few days??"
That's where we backed out a change that we landed a couple days before because it wasn't quite good enough. The change gave us a good perf boost but it broke some content so it was reverted. The overall trend is still downward which is a good thing. I'm not sure about the IE stats but I have seen gecko go head to head with every Mac browser available and it stomped them all in performance. I think we're pretty close with win IE but I don't know for sure. How about testing for us and reporting back here?
It is both good and bad that AOL has decided to use Mozilla in the next AOL release. Unfortunately they are applying pressure to the Mozilla team to wrap it up and get the product out the door.
This is a rediculous statement. AOL could care less about when 1.0 ships. Netscape 6.x and other AOL efforts haven't been delayed in their prior releases becuase Mozilla wasn't yet at 1.0.
The pressure to make a 1.0 comes from within Mozilla, not from outside. We have a great set of technologies and it's time to let the world know. There are dozens of commercial projects (and even more non-commercial) using Mozilla technologies and we're working hard to give them a stable and long lived 1.0 branch on which to work. The 1.0 release is just the beginning for many consumers of Mozilla code and it will ba a fine place to start.
We've still got a ways to go here. Check-ins to the tree are being tightly managed by the Mozilla "drivers" and we're working on getting it into shape for branching. When we get a handle on a few more bugs we'll create a Mozilla 1.0 branch and do a fairly quick Release Candidate 1. This will be a preview of what's to come with the final Mozilla 1.0 and an oportunity to gather feedback and TalkBack crash data that we will respond to over the following weeks as we approach the Mozilla 1.0 release.
I'm not sure what you're doing but Java works for me for the applets I've tested. Download and istall Sun's 1.3.0_0x and copy the NP* files to your plugins folder in the install directory or to a plugins folder you create in your Application Data/Mozilla/ directory. Do this with Mozilla not running and when you start it up it should work.
If this doesn't work then type about:plugins and see if the Java plugin shows up in the list. If it's not there then you didn't put it in the right place. If it is there then go to java.sun.com and click on the applets link in the left nav area of the page. Test some of the games and other applets there and they should work.
Be patient. The volunteers that have been doing this work for you in the past haven't gotten to it yet.
-Asa
Re:Two things that need to be fixed...
on
Mozilla 0.9.9 Released
·
· Score: 5, Informative
You should try 0.9.9. Both of your problem areas have received a lot of attention in 0.9.9 and should be greatly improved from your experience in 0.9.8.
According to the road map, Mozilla 1.0 will be out March 27th. Only 16 more days. Of course, according to the roadmap, 0.9.9 was supposed to be out a month ago.
Unlike most people actually working on this project and other Mozilla-based projects, you don't know how to read the roadmap. Those aren't even the branch dates. Those are the freeze dates when the tree is closed to all but approved checkins. A week or so after the freeze is the branch for that Milestone. But, guess what, that's still not the release date. That's the date that the development for that relase goes onto a branch and there is parallel development for the release branch and the development trunk. During that time the branch takes strictly monitored fixes and at some point on the branch (for most milestones it's a week or so) the release tag is made and binaries are served up to the testing community. All of this becomes a little more obvious if you read the roadmap in addition to looking at the pretty picture (even just looking at the picture and reading the key would help a lot)
Slashdot Mirror
Bank of America is my bank and it works just fine in Mozilla and Netscape 7 PR1.
--Asa
I notice they're using the May 31st 1.0-branch build as 1.0 . I'm on the 2nd of June 1.0-branch build right now. Maybe they decided to junk several days' work due to mistakes.
:-)
Actually, we're already moving forward to Mozilla 1.0.1
--Asa
I want to personally thank everyone that downloaded Milestone and nightly testing builds and contributed feedback in the form of Bugzilla bug reports, TalkBack crash reports, comments in the newsgroups and at mozillaZine.org. And a special thanks to those people that gave a hours, weeks, months or years of their lives to the care and feeding of our bug database (triage and testcasing bug reports). Without Mozilla's amazing QA and testing community we wouldn't be where we are today. ;-)
Oh, and all the developers too
AOL embeds a rendering engine in it's application. There are very few Mozilla usability issues in any embedded context since the majority of the UI is not Mozilla but rather the embedding application.
Right now AOL embeds a microsoft rendering engine in its AOL 7 client and a Mozilla rendering engine in its Compuserve cleint. Users shouldn't notice the difference between the microsoft and Mozilla rendering engines. Your usability arguement doesn't make a lot of sense in the embedded context (with the exception of web applications and other "in content" usability issues).
--Asa
This was the perfect earthquake for an earthquake virgin like me. It was just strong enough to know that it wasn't my imagination but not so strong that anyone got hurt or any property got damaged. I'm in Redwood City, CA and it was a thrilling experience.
--Asa
duh. I didn't see that it was you.
:)
--Asa
If you look at what actually happened this feature was removed for 1.0, not for the 1.1. And if you look even closer you will see that it wasn't disabled because of 1 bug. It was disabled because of performance problems and incompatability with tabbed browsing.
--Asa
Because the page that comes up comes up for all previous builds. They all suffer (except RC1) and it was easier this way.
--Asa
There are talkback nightly builds for linux. If you can reproduce a crash consistently then file a bug. You don't have to have a stack if you can repro regularly. If it's reproducible then someone else can get the stack.
--Asa
This doesn't fix a security hole from RC1. RC1 didn't have that security hole (it was obscured by the entire feature not working). Mozilla 0.9.9 did have the hole and it's now fixed in RC2. But this is not a security release. This release didn't happen because of the security fix (you could get that in a nightly builds many many days ago). This was a planned release based on feedback from RC1. We fixed 270 bugs between RC1 and RC2 including the most frequently encountered crash and hang problems.
--Asa
Did you install on top of a previous install? If you did then remove that install and start fresh (you won't lose your profile, it's stored in a different location).
--Asa
You've not been paying much attention lately. It's fixed.
--Asa
The Mozilla 1.0 branch is planned as a long-lived stability branch with minimal or no new features. Folks looking for a stable and slower-moving codebase on which to build other applications should have an easier time tracking the 1.0 branch than the fast and furius trunk which will be taking features and other destabilizing changes on the road to Mozilla 2.0.
--Asa
Bugzilla is not the place for an "ordinary customer". Bugzilla is a bug database, not a support forum. Ordinary customers need support and should use browsers, like Netscape 6.2, that offer support. Mozilla makes binaries available for testing and it is testers and developers for which our bug tracking tool is designed.
--Asa
A better question might be "Why is there a big spike up for all of the platforms over the last few days??"
That's where we backed out a change that we landed a couple days before because it wasn't quite good enough. The change gave us a good perf boost but it broke some content so it was reverted. The overall trend is still downward which is a good thing. I'm not sure about the IE stats but I have seen gecko go head to head with every Mac browser available and it stomped them all in performance. I think we're pretty close with win IE but I don't know for sure. How about testing for us and reporting back here?
--Asa
It is both good and bad that AOL has decided to use Mozilla in the next AOL release. Unfortunately they are applying pressure to the Mozilla team to wrap it up and get the product out the door.
This is a rediculous statement. AOL could care less about when 1.0 ships. Netscape 6.x and other AOL efforts haven't been delayed in their prior releases becuase Mozilla wasn't yet at 1.0.
The pressure to make a 1.0 comes from within Mozilla, not from outside. We have a great set of technologies and it's time to let the world know. There are dozens of commercial projects (and even more non-commercial) using Mozilla technologies and we're working hard to give them a stable and long lived 1.0 branch on which to work. The 1.0 release is just the beginning for many consumers of Mozilla code and it will ba a fine place to start.
--Asa
We've still got a ways to go here. Check-ins to the tree are being tightly managed by the Mozilla "drivers" and we're working on getting it into shape for branching. When we get a handle on a few more bugs we'll create a Mozilla 1.0 branch and do a fairly quick Release Candidate 1. This will be a preview of what's to come with the final Mozilla 1.0 and an oportunity to gather feedback and TalkBack crash data that we will respond to over the following weeks as we approach the Mozilla 1.0 release.
--Asa
I'm not sure what you're doing but Java works for me for the applets I've tested. Download and istall Sun's 1.3.0_0x and copy the NP* files to your plugins folder in the install directory or to a plugins folder you create in your Application Data/Mozilla/ directory. Do this with Mozilla not running and when you start it up it should work.
If this doesn't work then type about:plugins and see if the Java plugin shows up in the list. If it's not there then you didn't put it in the right place. If it is there then go to java.sun.com and click on the applets link in the left nav area of the page. Test some of the games and other applets there and they should work.
--ASA
How do I get it to launch into the browser automatically without first selecting the profile? Is there a command flag to specify the profile?
./mozilla -P "<profile name>"
run
--Asa
> How does one install Netscape plugins into
.mozilla directory so you don't have to start over when you do a new install (new to 0.9.9)
> mozilla on unix and windows?
>>Just drop the shared libs in the plugins/ dir
>>in the Mozilla install directory.
Or put them in a dir called plugins in your
--Asa
Linux users unite... Go vote for fullscreen (other platforms)
How about "Linux users unite... Go implement fullscreen for Linux Mozilla" ?
--Asa
Be patient. The volunteers that have been doing this work for you in the past haven't gotten to it yet.
-Asa
You should try 0.9.9. Both of your problem areas have received a lot of attention in 0.9.9 and should be greatly improved from your experience in 0.9.8.
--Asa
Actually, if it happened it would be 0.9.10
--Asa
According to the road map, Mozilla 1.0 will be out March 27th. Only 16 more days. Of course, according to the roadmap, 0.9.9 was supposed to be out a month ago.
Unlike most people actually working on this project and other Mozilla-based projects, you don't know how to read the roadmap. Those aren't even the branch dates. Those are the freeze dates when the tree is closed to all but approved checkins. A week or so after the freeze is the branch for that Milestone. But, guess what, that's still not the release date. That's the date that the development for that relase goes onto a branch and there is parallel development for the release branch and the development trunk. During that time the branch takes strictly monitored fixes and at some point on the branch (for most milestones it's a week or so) the release tag is made and binaries are served up to the testing community. All of this becomes a little more obvious if you read the roadmap in addition to looking at the pretty picture (even just looking at the picture and reading the key would help a lot)
--Asa