“People often ask “Why should Mozilla have a 1.0? Why
not just keep going and let vendors pick good milestones
retrospectively?” There are several reasons to do a 1.0, enumerated
below. But let’s agree on what a “Mozilla 1.0” would be:
- The first major-revision-number milestone release (mozilla1.0)
of the Mozilla browser application suite and platform from
mozilla.org. A release of higher quality than any delivered so far,
on whose quality our reputation is at stake precisely because 1.0
is such a coveted and feared version number.- A set of promises to keep compatibility with various APIs,
broadly construed (XUL 1.0 is an API), until a 2.0 or
higher-numbered major release. All milestone releases and trunk
development between 1.0 and 2.0 will preserve frozen interface
compatibility. Mozilla 1.0 is a greenlight to hackers,
corporations, and book authors to get busy building atop this
stable base set of APIs.- A stable, long-lived branch off of the cvs.mozilla.org trunk
(MOZILLA_1_0_BRANCH). Interested parties should collaborate, with
support from staff@mozilla.org, in developing conservative fixes
for critical bugs in this branch. Anyone who wants a baseline for
development that will work with the public APIs of Mozilla 1.0 is
free to develop against the 1.0 branch.
Articles
View All Hover to load posts
Articles
View All Hover to load posts
Articles
View All Hover to load posts
Articles
View All Hover to load posts
Articles
View All Hover to load posts
Articles
View All Hover to load posts
Articles
View All Hover to load posts
Articles
View All Hover to load posts