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
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 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. 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 assume NS will start to release more frequent
updates once Mozilla 1.0 is released which they should (if rumor holds true
on the numbering) brand a Netscape Communicator 6.5 with all there marketing
garbage attached.
Just a couple things to think about and my $0.02 added,
MJ
