My two cents on Mozilla 1.0:

I think the discussion has prematurely focused more on the details 
rather than clarifying the
big picture. In other words, I think it essential to come up with a 
succinct "vision statement" defining
the general purpose of the 1.0 release. Examples:

"1.0 will be competitive with or surpass IE in terms of standards 
support and the user
experience." (perhaps too ambitious)

"1.0 will replace Netscape 4.x" (still a stretch, IMO)

"1.0 will be a stable platform for further development involving greater 
participation from
  the open source community." (implies API freeze, massive documentation 
effort)

"1.0 will be sufficiently stable and functional for people to use as an 
every day browser, mail and news
reader." (0.9.2 is practically there)

etc. etc.

Following the expression of the vision statement, you can define 
specific areas of functionality
and performance to support the vision. Finally, you define the metrics 
you will use to measure
your success and the procedures you will use to obtain the data.


Reply via email to