Mozilla Tries New "Lorentz" Dev Model 126
With the recent release of Firefox 3.6, Mozilla has also decided to try out a new development model dubbed "Lorentz." A blend of both Agile and more traditional "waterfall" development models, the new methodology aims to deliver new features much more quickly while still maintaining backwards compatibility, security, and overall quality. Only time will tell if this is effective, or just another management fad. "If the new approach sounds familiar, that's because Unix and Linux development has attempted similar kinds of release variations for iterating new features while maintaining backwards compatibility. HP-UX, for example, is currently on its HP-UX 11iv3 release, which receives updates several times a year that add incremental new functionality. The Linux 2.6.x kernel gets new releases approximately every three months, which include new features as well."
Chaotic releases? (Score:4, Funny)
Is this chaotic release schedule supposed to be more attractive?
Pointless, unles... (Score:1, Funny)
Can I use the theory of special relativity to get out of missed deadlines? Sure, we are way behind in this frame of reference. But as viewed from a different frame of reference traveling near the speed of light relative to us we shipped yesterday!
And they are moving their servers to Amman (Score:2, Funny)
Thank you, thank you, I'll be here all week! Try the lamb!
Scheduling (Score:5, Funny)
Plus, with the "Lorentz" transformation, time dilation makes it a lot easier to hit release dates. But there has been some concern over the developers' sudden weight gain.
Re:Chaotic releases? (Score:5, Funny)
Re:Chaotic releases? (Score:4, Funny)
Again, I request a "+1 Badum-tish"
Re:Chaotic releases? (Score:2, Funny)
Releasing when a feature is ready sounds both chaotic and reasonable. Chaotic is not neccessarily bad.
Three words: Duke Nukem Forever.
*ducking*
Re:Chaotic releases? (Score:5, Funny)
We use the "Homer" Methodology... (Score:2, Funny)
Re:Oh god, the still use Waterfall? (Score:3, Funny)
Oh, pfft. The thing that killed Duke Nukem Forever was the decision to implement it in Perl 6.
the universe is predjudiced! (Score:3, Funny)