Several people have asked me whether Mozilla's move to rapid releases has helped or hurt Firefox's security. I think the new cadence has helped security overall, but it is interesting to look at both the ways it has helped and the ways it has hurt. Security of new features With release trains every 6 weeks, developers feel less pressure to rush half-baked features in just before each freeze. Combi
Open issues/risks ` Stage 1: Definition 1. Feature overview This feature falls under the Experience theme. With the transition to the Rapid Release development model, the frequency in which we interrupt a user's workflow will be increasingly more common. With goals to offer a secure, feature-rich, and fun browsing experience, we want to ensure everyone is on the latest version of Firefox. To achie
Recently Mozilla implemented a rapid release process, where we release a version of Firefox every 6 weeks. This has involved changing a number of our processes. It’s also raised some new issues. For example, some enterprises find the idea of rapid browser change to be disconcerting at best and potentially unmanageable at worst. Add-on compatibility is another. I acknowledge these issues are com
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く