This is a bizarre naming. They could call it Blaze installer 2.0 for Blaze 1.
This is how Bazel rolls out incompatible changes:
- Introduce a new behavior behind a flag
- Wait
- If there was no push back (and key projects could migrate), flip the flag to enable the new behavior by default.
The goal is to give an opportunity for users to update their code in advance, and get feedback about migration issues.
This is how Bazel rolls out incompatible changes:
- Introduce a new behavior behind a flag
- Wait
- If there was no push back (and key projects could migrate), flip the flag to enable the new behavior by default.
The goal is to give an opportunity for users to update their code in advance, and get feedback about migration issues.