Tag: Codename Namoroka

Firefox 3.6 Beta 1 Up Next

September 20, 2009 by Jason

Mozilla is working its way to deliver the first beta development milestone of Firefox 3.6., codename Namoroka. The next iteration of the open-source browser won’t have any additional Alpha releases and will advance straight to Beta, with the final release planned for just two months away. At the start of this week, Mozilla noted that the Beta 1 Build for Firefox 3.6 is the next development milestone of Namoroka, indicating that the v3.6 minor update for Firefox is evolving fast toward general availability.

String freeze in common code and browser only took place on September 15th, just to be extended to all aspects of Firefox 3.6 the subsequent day. As far as Mozilla is concerned, the upcoming deadline in the development process of Firefox 3.6 is Beta code freeze. “Right now we’re potentially drifting into November for a final release due to [a] number of outstanding blockers,” Mozilla noted on September 16th.

The Beta 1 for Firefox 3.6 was initially planned for availability by the end of September 2009, and with the progress made by Mozilla so far it looks like, by the end of this month, users will be able to test drive the first post-Alpha release of v3.6. Firefox 3.6 Alpha 1 was offered to testers in the first half of August 2009, more than a month ago. Read More»

Codename Namoroka from Firefox

April 04, 2009 by Jason

With Firefox 3.1 evolved into Firefox 3.5 in the move from Beta 3 to Beta 4, Mozilla is also looking ahead beyond Shiretoko, to the next iteration of its open-source browser. Firefox Next will be codenamed Namoroka and the version number for the project will be 3.6, although this will only be valid for the initial stages. Mozilla in fact refers to what will be the successor of Firefox 3.5 as Firefox.next. Namoroka will be based on the Gecko 1.9.2 rendering engine, and is currently planned for availability in the first half of 2010.

“In contrast to previous product planning exercises, which were declarative and relatively inflexible, we hope to develop this project in a highly iterative manner by which we initially declare project goals and prioritized areas of interest for investigation, and then spend time determining the exact shape and scope of feature development tasks. The outcome of these investigations will be a set of feature design documents (using a common template) which will be prioritized and constitute the final product development plan,” revealed Mike Beltzner, Director of Firefox at Mozilla Corporation. Read More»