With a June release for Firefox 5 (scheduled), this link tells what Mozilla developers are implementing very soon. Every 2 to 4 months (max) they expect to put out a new release. Apple tried that with 1 year releases on OSX and had to go back to 2 years releases and Microsoft doesn't even try to meet such a short turnaround.

Read more here.

http://people.mozilla.com/~sayrer/2011/temp/process.html

P.S. Eighteen, not sixteen weeks as I originally thought.

N



Edited 2 time(s). Last edit at 04/12/2011 06:26PM by ndebord.

Proposed Mozilla rapid release (Nightly/Aurora/Beta/Final) development schedule:

http://mozilla.github.com/process-releases/draft/development_specifics/

More on how this new, rapid development scheme might affect other Gecko browsers, like Seamonkey.

http://forums.mozillazine.org/viewtopic.php?f=6&t=2162687

N

yup. just wondering if K-meleon will follow the mozilla rapid development releases.
they're moving at a much faster pace than how new K-meleon versions have been released.

Quote
4td8s
yup. just wondering if K-meleon will follow the mozilla rapid development releases.
they're moving at a much faster pace than how new K-meleon versions have been released.

4td8s,

If you have $80 million or so in spare change to donate to the K-Meleon developers, I'm sure they can speed up release dates just like Mozilla Corporation!!! <wry grin>

N



Edited 1 time(s). Last edit at 04/30/2011 12:51AM by ndebord.

well firefox 5 beta will be offered in mozilla's beta channel on may 17 and the final release of firefox 5 is scheduled to come out on june 21. i'm not joking on either one of those.

and soon, seamonkey will start following mozilla's rapid release process as well.
read this recent blog here:
http://home.kairo.at/blog/2011-05/weekly_status_report_w17_2011

Quote

Also, it more and more looks as if SeaMonkey will chime in with the rapid release process and produce small but fast updates in the future, which also should get exciting.

Edited 1 time(s). Last edit at 05/11/2011 06:38PM by 4td8s.

Quote
4td8s
well firefox 5 beta will be offered in mozilla's beta channel on may 17 and the final release of firefox 5 is scheduled to come out on june 21. i'm not joking on either one of those.

and soon, seamonkey will start following mozilla's rapid release process as well.
read this recent blog here:
http://home.kairo.at/blog/2011-05/weekly_status_report_w17_2011

Quote

Also, it more and more looks as if SeaMonkey will chime in with the rapid release process and produce small but fast updates in the future, which also should get exciting.

For long time I've been using firefox betas (before its 1.0 first official rel) because it was lean, fast, and had no useless junk built-in. But as soon as bloat started to pour-in into this once fine browser, around version 0.6 or 0.72 or 0.9 (been long time, I'm sure I'm confusing FF versions with K-M versions), anyways it was obvious in which direction it will go, and that's when I decided to switch to K-Meleon for good (it also helped that K-M got updated to a very usable browser at that time).
Do you see where I'm going with it?
I, for instance, couldn't care less if new firefox is released on a weekly basis.
All the changes I have seen in all firefox versions are just more bloat, with very seldom truly useful feature that most users would need or desire. That's the reason why I'm still using K-Meleon. The only thing that K-M needs is official gecko updates (which ought to be posted on the main page next to the official downloads, as I always ask for this...).
Want bloated browser or need to install newer browser versions every few weeks? Well, there is firefox for that.
I don't want it, and I'm sure neither do most of K-Meleon users.

Quote
4td8s
well firefox 5 beta will be offered in mozilla's beta channel on may 17 and the final release of firefox 5 is scheduled to come out on june 21. i'm not joking on either one of those.

and soon, seamonkey will start following mozilla's rapid release process as well.
read this recent blog here:
http://home.kairo.at/blog/2011-05/weekly_status_report_w17_2011

Quote

Also, it more and more looks as if SeaMonkey will chime in with the rapid release process and produce small but fast updates in the future, which also should get exciting.

45d8s,

Yup, and FF 5 is really just FF 4.0.2, as they backed out a lot of the promised miracle changes when they got around to releasing FF 4 (after 12 betas!).

In the past, security issues that affect FF and SM often don't affect KM, so we will have to keep a close watch on Gecko 1.9.1 and Gecko 1.9.2 to see what's actually happening that is pertinent to KM.

N

Quote
ndebord
With a June release for Firefox 5 (scheduled), this link tells what Mozilla developers are implementing very soon. Every 2 to 4 months (max) they expect to put out a new release. Apple tried that with 1 year releases on OSX and had to go back to 2 years releases and Microsoft doesn't even try to meet such a short turnaround.

Read more here.

http://people.mozilla.com/~sayrer/2011/temp/process.html

P.S. Eighteen, not sixteen weeks as I originally thought.

no ndebord. SIX WEEKS!

read this and weep-
https://wiki.mozilla.org/RapidRelease

a little quote from that page in the "Merge and Release Dates" section:

Quote

...and so on, every six weeks.

Edited 1 time(s). Last edit at 07/11/2011 04:55AM by 4td8s.

Okay, every six weeks a few more bugfixes
So it looks like they switched from "major changes" on X.X.0 numbers and yet bigger ones on full numbers X.0.0, to major changes on X0.0.0 - just moving a dot one number to the left side, who cares? Cannot take that idiocy seriously sorry, it's just playing with numbers like faking (oops polishing) statistics...



Edited 3 time(s). Last edit at 07/11/2011 05:55AM by siria.

Quote
siria
Okay, every six weeks a few more bugfixes
So it looks like they switched from "major changes" on X.X.0 numbers and yet bigger ones on full numbers X.0.0, to major changes on X0.0.0 - just moving a dot one number to the left side, who cares? Cannot take that idiocy seriously sorry, it's just playing with numbers like faking (oops polishing) statistics...

Siria,

Siria,

The weasel (G) in the hen house is Debian, which uses FF 3.6.xx for its iceweasal version of FireFox. According to what I've read, they want to keep using Gecko 1.9.xxx for now, which is good for KM 1.7.

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20110323 Iceweasel/3.5.16)

Just read this from MacWorld. "Mozilla has decided to issue at least one more security update for that edition, which shipped in January 2010. The update, to be pegged 3.6.19, will be released alongside Firefox 6 when the latter ships on Aug. 16."

N



Edited 1 time(s). Last edit at 07/11/2011 02:22PM by ndebord.

the chrome factor

Quote
disrupted
the chrome factor

;-)

N

Quote
disrupted
the chrome factor

disrupted,

Very nice and I assume you also saw this "The Enterprise is Dead to Me - Hitler" you tube video posted over in MozillaZine?

http://www.youtube.com/watch?v=kq8s-Rubs5w




N



Edited 1 time(s). Last edit at 07/12/2011 06:53PM by ndebord.

Quote
ndebord

Quote
disrupted
the chrome factor

disrupted,

Very nice and I assume you also saw this "The Enterprise is Dead to Me - Hitler" you tube video posted over in MozillaZine?

http://www.youtube.com/watch?v=kq8s-Rubs5w

nah, actually didnt see it before.. i guess the guy with the funny moustache is asa
"don't worry, we can always fork the code base" that was hilarious!

Disrupted,

All of it funny, now to try and find out if Debian is serious about sticking with FF 3.6 (aka IceWeasal) for some extended period of time, perhaps enough to let us sort out future releases of KM???

N

The Firefox world loses John J. Barton (a Web dev guru that contributed to Firebug) to Chrome.

Quote
Stephen Shankland
For years, an extension called Firebug has been a powerful tool that kept Web programmers loyal to Firefox.

Quote
John J. Barton
Basing next gen work on Firebug is not practical. The pace of change in browsers is too fast for our team size. Firebug hasn't really been able to keep up with Firefox, let alone compete with other tools.

So IMHO there seem to be some casualties of Mozilla's new rapid-release program for Firefox.



Edited 1 time(s). Last edit at 07/19/2011 09:31AM by guenter.

More casualties to read here http://adblockplus.org/blog/binary-xpcom-components-are-dead-js-ctypes-is-the-way-to-go with interesting links and comments.

Consequence of rapid release?

Quote
j_k
More casualties to read here http://adblockplus.org/blog/binary-xpcom-components-are-dead-js-ctypes-is-the-way-to-go with interesting links and comments.

j_k, read this blog by Wladimir Palant on rapid releases and version numbers:
On rapid releases and version numbers

Quote
surfer
Consequence of rapid release?

surfer & j_k, read the following blogs by Kairo and Jesse Ruderman:

Rapid releases and security

Why Rapid Releases Can Improve Stability



Edited 1 time(s). Last edit at 08/31/2011 10:35AM by 4td8s.

Nobody doubts that the rapid release also has advantages e.g. for security

Quote
Pete's Comment in Kairo's blog
but paying that with losing enterprises and extensions seems for me too expensive.

So there are great contras coming with it too.



Edited 1 time(s). Last edit at 08/31/2011 05:56PM by guenter.