Reply to post: Re: The snag with a four-week release cycle ...

Firefox 79: A thin release for regular users, but plenty for developers to devour

Len
Go

Re: The snag with a four-week release cycle ...

Why would a time based release cycle produce more bullshit code? As there is no list of arbitrary goals that need to be met to call something a release one could even argue that it produces fewer irrelevant code.

Obviously, time based cycles are useless if you are just a handful of developers all working on the same thing.

If, like Mozilla, you are hundreds of developers who work on a high complexity product with dozens of completely unrelated sections then time based releases make a lot of sense. Every week one or two teams complete a major feature or change, in the current process it takes only eight weeks (one alfa and one beta cycle) before end users get to benefit from it.

That speed is very useful for a dynamic environment such as the web.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon