It doesn't mean we'll be shipping more features, or shipping new features in less time. Shifting to a faster release cycle allows us to experiment and iterate on new features more effectively via origin trials, without having to wait as long between releases. And for developers, you won't have to wait as long for updates and bug fixes. Moving to a four-week release cycle will give us more agility to get critical security and bug fixes out to users faster. I can fix a critical bug and deploy it to all of my users quickly. One of my favorite aspects of being a web developer is the ease of deployment. ![]() There's more detail on the Chromium Blog about the impetus and rationale for this change. ![]() Later this year, we plan to shorten the release cycle and ship a new version of Google Chrome to the stable channel every four weeks, down from the current six-week cycle.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |