d89a45b9cd
Currently, the vast majority of chromium builds run on jammy. And after https://crrev.com/c/4652993, any new builder will automatically be running on jammy. So jammy is now the official default for infra jobs. This updates the docs to mention that, and clarifies them a little since the statement about "most development" might apply to more than just CI builds, and we can't be as confident about the OS breakdown outside of our infra. Bug: 1412588 Change-Id: I751abf251db9758c0b6c12733a2e06f7a5e3e5c4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4654783 Commit-Queue: Ben Pastene <bpastene@chromium.org> Reviewed-by: Thomas Anderson <thomasanderson@chromium.org> Cr-Commit-Position: refs/heads/main@{#1163837}
Chromium
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead,
follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.