Mike Jaques wrote:
> Namely creating a stable branch, and a
> development trunk, of which minor bug-fixes and regression-tested
> enhancements will go, and the trunk for the mainstream melee of regression
> and development work? A branch-point at version. 1.0, leading to 1.0.1
> 1.0.2 and so on, while development on the trunk will be deemed 1.1.1, 1.1.2
> and so on.
I expect development to run further just like it happens now!
But IMHO there needs to be some aims for a 2.0 version, just like it was
CSS, HTML 4.0, etc support and a complete suite of applications for 1.0.
For example, a full implementation of CSS 3.0, XSL, complete SVG support
and some most frequently wished (we will see which these are after the
1.0 release) features (just a few thoughts: a download manager, make
composer output css styled pages or even XML documents, ... - more
ideas?). And, of course, fix all remaining bugs - means: as many as
possible ;-)
> I am musing this because once 1.0 comes out, I fear that it will suffer the
> same fate as all milestones in the past, and it wont be continued to be
> improved upon.
Milestones are done for one reason: give an overview of the progress,
not for having 20 branches until 1.0
> It should be given different treatment since its been deemed
> release quality for mass consumption. And those looking for a stable
> frequently bug fixed product (glaring bugs, minor UI improvements, minor
> usability updates, as well as anything an independent developer wants to add
> as long as he goes through the normal r/sr channels) will have no choice but
> to use a Netscape product.
I see your point - agreed! the trunk is too heavily changing for any
minor improvements
> I assume NS will start to release more frequent updates
just like NS 4.71, 4.72, 4.73, 4.74, 4.75, 4.76, 4.77, 4.78 - don't know
the current standings - haven't donwloaded a release since 4.6x! Hope
they will not, at least not in this way.
just my €0.02...
Regards,
Niko!
