| commit | 3554e5d841882da1bf451351ec2982389a4b7984 | [log] [tgz] |
|---|---|---|
| author | Googler <pcloudy@google.com> | Wed Sep 14 09:57:15 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Sep 14 09:58:51 2022 -0700 |
| tree | 8c72fcd556edda78eabde649df028092bd6fa21f | |
| parent | 390d212d76e91f413f143b53a997b0bf846c453a [diff] |
Update incompatible change process on when to close github issue Previously, we stated that the incompatible flag issue should be closed when the flag is removed from HEAD (instead of flipped). But this doesn't work well because it makes tracking the flag flip harder, which is problematic for two use cases 1) Using the issue as a release blocker. Before cutting a release, we only care if the flag is flipped, not if it's removed. 2) The incompatible flag pipeline should stop test the flag after it's flipped. Keeping the issue open will confuse the pipeline. Therefore, we update the policy to close the incompatible issue when the flag is flipped, then file another issue to track the removal of the flag. RELNOTES: PiperOrigin-RevId: 474320452 Change-Id: Ida825a3c41575a940cc2082f4fc2cfae449a6f03
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
