Project: SCL3. What powers growth? | Mozilla IT
What drives Mozilla IT’s data center growth? You do. I can break down the machines in the data center into three sections (and this is a very simplistic view): Classic infrastructure. All the web sites and infrastructure to support Mozilla and Firefox. Release Engineering. All the infrastructure that builds and tests Firefox. Services. Right now mostly Firefox Sync but will soon include BrowserID
Home of KaiRo: Firefox 7.0.1 updates to 8.0.1, but 8.0 doesn't?
<< Firefox 7.0.1 aktualisiert auf 8.0.1, aber 8.0 nicht? | The roads I take... | Integration eines Magento-2-Webshops mit FreeFinance und selbstgebautem Warenmanagement >> Firefox 7.0.1 updates to 8.0.1, but 8.0 doesn't? I found the following question being raised on German newsgroups, but I guess there's more people interested in this: I found out that on one of my computers Firefox 7.0.1 has bee
Releases/Firefox 9/Ship options - MozillaWiki
There has been some previous and more recent discussions about Firefox 9. We need to decide on a release plan. I provide a couple of options here, some pros and cons, and some basic assumptions. Please feel free to correct what I have written, suggest other options, or provide additional insight. Basic Assumptions We want to release Firefox 9 This was established at a previous meeting. Firefox 9 h
tech ramblings » Blog Archive » Rapid releases: one webdev’s perspective
People still seem to be very confused about why Mozilla has moved to the new rapid release system. I thought I’d try and explain it from my perspective. I should point out that I am not any kind of official spokesperson, and should not be quoted as such. The following is just my own personal opinion. Imagine, now, you work on a team of web developers, and you only get to push new code to productio
Weekly Engineering Newsletter 2011-07-20 - mozilla.dev.planning
Welcome to the 27th issue of the Weekly Engineering Newsletter, where each week I bring you all the engineering news you need to know and only a tiny bit you don't. Even better, it comes in a dose that's less than 500 words. More news. Less noise.OK, let's go! *Planning Update* We're one third of the way through the Firefox 8 cycle. During this last week, engineers landed fixes for 200 bugs and fe
Release Management Blog
Release Management Blog Thoughts and facts on shipping quality software by the team that ships Firefox every 4 weeks We work hard as an organization to ship the best browser possible every 4 weeks with about 1000 new patches per release. We ship new features to make our browser useful and easy to use. We also do platform work to be able to render new sites and web applications while remaining comp
Release Management Blog
Release Management Blog Thoughts and facts on shipping quality software by the team that ships Firefox every 4 weeks We work hard as an organization to ship the best browser possible every 4 weeks with about 1000 new patches per release. We ship new features to make our browser useful and easy to use. We also do platform work to be able to render new sites and web applications while remaining comp
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
713964 - Unthrottle FF9.0.1 updates at 10% until we get to ~15million users
Goals for "landing code" experience? - mozilla.dev.planning
XUL Fennec, Android tablets, and nightly updates - mozilla.dev.planning
TestEngineering/Performance/Talos - MozillaWiki
Software Update:MAR - MozillaWiki
chris' random ramblings
GoFaster: deeper data analysis
Shipping Type Inference and Other "Irreversible" Changes - mozilla.dev.planning
Public Service Announcement: Merge project branches to m-c, not m-i - mozilla.dev.platform
Firefox/Beta/2011-08-08 - MozillaWiki
Upcoming changes to nightly builds - mozilla.dev.planning
Error
ReleaseEngineering/BuildFaster/Meetings/2011-07-07 - MozillaWiki