Roadmap - Bazel

This document describes the Bazel team's plans for introducing features that will be incorporated into version 1.0. Note that this roadmap only includes features that the Bazel team itself intends to support. We anticipate that a number of other features will be added by code contributors.

For the alpha and beta releases, the Bazel team will maintain two code repositories:

• A Google-internal repository, containing both Bazel code and Google-specific extensions and features
• An external GitHub repository, containing only the Bazel code.

We anticipate making the external repository primary in the future, that is, code from Google and non-Google contributors will be committed and tested in the external repository first, then imported into the internal repository. For the alpha and beta releases, however, the internal repository will be primary. Changes to Bazel code will be frequently pushed from the internal to the external repository.

In the following table, each feature is associated with a corresponding milestone. The convention for the priorities are:

• P0 feature will block the milestone; we will delay the milestone date until the feature is shipped.
• P1 feature can delay the milestone if the feature can be shipped with a reasonable delay (2 months max).
• P2 feature will be dropped and rescheduled for later rather than delaying the milestone.

We will update this list when reaching each milestone; some milestones may also be refined if appropriate.