> Ok, I know its early, and I don't want to too much open up a can of worms,
> but I was wondering if any thought has gone into a post 1.0
> release/development scheme. Namely creating a stable branch, and a
> development trunk, of which minor bug-fixes and regression-tested
Regression tests? Oh, if we had an automated set of those...
> 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.
Is this a "fate"? Milestones, in and of themselves, are an indication of
progress, not the basis for a stable product (unless contributing
organisations choose to work on them to make them so, which has so far
happened once.)
> 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.
There is a strong argument that this is exactly what Netscape are there
for. :-) On the other hand, I assume that they will work on the 1.0 branch
from which they release (assuming they do) a lot more than the 0.6 branch,
because the product they release from it will kick ass ;-)
I think that mozilla.org's focus should not be on improving stable
branches, but on taking the product forward. If individual contributors or
contributing organisations wish to focus their resource on stable
branches, that's cool, and we can reap the benefits.
Gerv
