There are so many things I disagree with about this idea that it's tough to know where to start :-) Firstly, this automatically assumes that end-user experience is the defining criteria for Mozilla 1.0. This is by no means a given. Secondly, it assumes that you can find some company willing to let us use its employees as guinea pigs. Thirdly, it's extremely arbitrary, as you yourself said. What if the percentage sticks at 49%? Do we keep working for another six months until we persuade one more person to switch? I understand that we need to flag and fix usability issues, and I believe that they are getting flagged, at least, using mechanisms like nsCatFood. But I don't believe that usability studies should define the Mozilla release schedule. Gerv
- A proposed Moz 1.0 release criterion Randall Parker
- Re: A proposed Moz 1.0 release criterion RV
- Re: A proposed Moz 1.0 release criterion Randall Parker
- Re: A proposed Moz 1.0 release criterion RV
- Re: A proposed Moz 1.0 release criterion DeMoN_LaG
- Re: A proposed Moz 1.0 release criterion Mszlazak
- Re: A proposed Moz 1.0 release criterion Greg Miller
- Re: A proposed Moz 1.0 release criterion Syd Logan
- Re: A proposed Moz 1.0 release criterion Vineet Sinha
- Re: A proposed Moz 1.0 release criterion RV
- Re: A proposed Moz 1.0 release criterion Gervase Markham
- Re: A proposed Moz 1.0 release criterion Vineet Sinha
- Re: A proposed Moz 1.0 release criterion Randall Parker
- Re: A proposed Moz 1.0 release criterion Greg Miller
- Re: A proposed Moz 1.0 release criterion Randall Parker
- Re: A proposed Moz 1.0 release criterion Randall Parker
- Re: A proposed Moz 1.0 release criterion Josh Soref
- Re: A proposed Moz 1.0 release criterion Vineet Sinha
- Re: A proposed Moz 1.0 release criterion Scott I. Remick
- Re: A proposed Moz 1.0 release criterion Vineet Sinha
- Re: A proposed Moz 1.0 release criterion Greg Miller
