Kilimanjaro/FAQ
⚡ Warning: The content of this page is obsolete and kept for archiving purposes of past processes.
Q: What is Kilimanjaro?
A: Kilimanjaro is an integration milestone across several of our products. The Kilimanjaro Event is the point in time when we realize a tightly integrated set of products. It is important to point out that the Kilimanjaro Event is not a single release. It is an incremental effort where we deliver a series of releases and features to each of our products that result in and enable an end-to-end user experience across these efforts. When we reach the Kilimanjaro milestone we will have an elegant and simple experience for HTML5 Web apps in Firefox on multiple devices that puts the user in control of their apps and identity.
Q: Why is Mozilla doing this?
A: A people-centered experience powered by the Web (technology and principles!) that includes mobile devices doesn't exist and is sorely needed. Mozilla must lead the way, because we are the only organization who has no interest in or motivation to “own” the user; we believe the user is sovereign. A people-centered system will enable users to identify themselves to websites and apps on their own terms; to take their apps easily from one OS to another; to disclose only what they want about themselves in proportion to the value they receive. Only Web principles enable a level playing field without gatekeepers.
Q: If it’s not a product release, what will the results be?
A: When we reach the Kilimanjaro milestone we will have an elegant and simple experience for HTML5 Web apps in Firefox on multiple devices that puts the user in control of their apps and identity. For detailed information, see: https://wiki.mozilla.org/Kilimanjaro/ProductDraft
Q: When do we plan to reach Kilimanjaro?
A: Our proposed target date for this event is September 2012.
Q: How will we know when we’ve reached Kilimanjaro?
A: The Kilimanjaro milestone is "version 1.0" of the end-to-end user experience. Products will continue using their existing release vehicles, but we reach Kilimanjaro after these products are interoperable according to the requirements here: https://wiki.mozilla.org/Kilimanjaro/ProductDraft.
Q: What’s next after Kilimanjaro?
A: We expect there to be subsequent periodic milestones after Kilimanjaro that will continue to serve as integration points. Those milestones may nor may not be named after mountains.
Q: What does this mean for Firefox/rapid release schedule?
A: Firefox will continue to have regular release trains. This is simply an effort to align other Mozilla products as they become integrated w/Firefox.
Q: What does Kilimanjaro change about how we work?
A: Engineering has re-inspected our methods and processes in order to improve quality of features and releases. Today, the release trains run on time, and the desktop product is on a rhythm--shipping features and fixes on schedule. To augment the train model and enable us to realize this moment of integration, we are re-introducing the concept of blockers. We're adding a flag to Bugzilla, to all relevant components to enable anyone to nominate bugs or features that block the realization of the Kilimanjaro Event. We will re-introduce distributed triage by component owners as a driving mechanism for this event. Every team will be accountable for their blockers--even those teams and individuals who have never had blockers before.
