Netscape's Tentative Feature Complete Plans

Thursday March 16th, 2000

Jim Roskind has chimed in with the unofficial word on Netscape's plans for their browser in the months to come. Netscape is hoping to hit a May 2 "Feature Complete" date. The main issue is whether or not Netscape will be forced to "branch" - continue development of their product separately from the main Mozilla development. If that were to happen, it's safe to assume that along with that branch would come a redirecting of Netscape's great QA team to the commercial branch (which means that Mozilla could lose a lot of QA in the meantime). I tend to agree with Jim on this point. I would prefer that Netscape not branch until Mozilla is a bit more stable. Some work, however, still needs to be done to ensure Mozilla's identity apart from Netscape's commercial product (Mozilla can't continue on with Netscape's UI indefinitely). Hopefully something will be worked out where Netscape can continue on without branching for as long as possible, but Mozilla can continue to get improvements that will help it stand on its own. Check out Jim's post, and then tell us what you think.

#6 Re: Get Communicator OUT THE DOOR.

by sab39

Friday March 17th, 2000 7:45 AM

You are replying to this message

<< But hasn't it already branched? If not, why the different M15 and M15nb1b builds? >>

As mozAdmin said in another thread, this is a branch for beta1 only and isn't permanent - the "branch" discussed in this post would be more-or-less permanent.

<< Also, is this 5/2 date a beta1 date, which would mean that the hope to have beta1 by the end of March is now dashed? Somewhere in there I thought there was a beta preview, as well. >>

Actually, there was a followup on the original newsgroup in which jar clarified that this was talking about beta2 and beyond. Beta1 is still scheduled for about the time of 3.0, as far as I can tell (see <…ones/progress-2-beta.html> for a timeline, which unfortunately seems to be a couple days outdated but it looks like they're on or ahead of schedule for all of it).

As far as a permanent branch, I'd like to see this never happen - I'd rather see a series of short-term branches like the beta1 branch.

I agree that getting communicator out of the door as soon as possible is a high priority... but I think early branching would actually slow things down rather than speeding them up.