DCAWD.com

this article covers a presentation done by the chrome dev team. it's a really neat way to handle versioning and patches/releases. they've transformed versioning from a "features at a specific release number milestone" deal to a "more fluid, more consistent release schedule" deal. pretty cool.

my favorite quote from the article: "The versions start to blend together. The approach is more like updating a website than a piece of client software. The version numbers don’t really matter. What version of Amazon are you on? Exactly."

Looks like elements of RUP and XP development cycles... Nice to see it on such a big project.

Very cool read. Maybe more projects will starting using it. I'm guessing they think it's better than Waterfall or Agile... and it probably is, haha.