chromium: Update the documentation

And close #78450 because I'm maintaining Chromium for approximately one
year now and it looks like I can keep maintaining it (at least as long
as I have enough time for it). I'm also working on the documentation,
automation, and cleanups so finding a new maintainer in the future
should hopefully be easier.
This commit is contained in:
Michael Weiss 2021-02-07 13:39:58 +01:00
parent 1733a19b02
commit 89db67e734
No known key found for this signature in database
GPG key ID: 5BE487C4D4771D83

View file

@ -1,11 +1,11 @@
# Maintainers # Maintainers
- TODO: We need more maintainers: - Note: We could always use more contributors, testers, etc. E.g.:
- https://github.com/NixOS/nixpkgs/issues/78450 - A dedicated maintainer for the NixOS stable channel
- If you just want to help out without becoming a maintainer: - PRs with cleanups, improvements, fixes, etc. (but please try to make reviews
- Look for open Nixpkgs issues or PRs related to Chromium as easy as possible)
- Make your own PRs (but please try to make reviews as easy as possible) - People who handle stale issues/PRs
- Primary maintainer (responsible for updating Chromium): @primeos - Primary maintainer (responsible for all updates): @primeos
- Testers (test all stable channel updates) - Testers (test all stable channel updates)
- `nixos-unstable`: - `nixos-unstable`:
- `x86_64`: @danielfullmer - `x86_64`: @danielfullmer
@ -13,11 +13,14 @@
- Stable channel: - Stable channel:
- `x86_64`: @Frostman - `x86_64`: @Frostman
- Other relevant packages: - Other relevant packages:
- `chromiumBeta` and `chromiumDev`: For testing purposes (not build on Hydra) - `chromiumBeta` and `chromiumDev`: For testing purposes only (not build on
Hydra). We use these channels for testing and to fix build errors in advance
so that `chromium` updates are trivial and can be merged fast.
- `google-chrome`, `google-chrome-beta`, `google-chrome-dev`: Updated via - `google-chrome`, `google-chrome-beta`, `google-chrome-dev`: Updated via
Chromium's `upstream-info.json` Chromium's `upstream-info.json`
- `ungoogled-chromium`: Based on `chromium` (the expressions are regularly - `ungoogled-chromium`: @squalus
copied over and patched accordingly) - `chromedriver`: Updated via Chromium's `upstream-info.json` and not built
from source.
# Upstream links # Upstream links
@ -36,6 +39,11 @@ update `upstream-info.json`. After updates it is important to test at least
`nixosTests.chromium` (or basic manual testing) and `google-chrome` (which `nixosTests.chromium` (or basic manual testing) and `google-chrome` (which
reuses `upstream-info.json`). reuses `upstream-info.json`).
Note: The source tarball is often only available a few hours after the release
was announced. The CI/CD status can be tracked here:
- https://ci.chromium.org/p/infra/builders/cron/publish_tarball
- https://ci.chromium.org/p/infra/builders/cron/publish_tarball_dispatcher
To run all automated NixOS VM tests for Chromium, ungoogled-chromium, To run all automated NixOS VM tests for Chromium, ungoogled-chromium,
and Google Chrome (not recommended, currently 6x tests!): and Google Chrome (not recommended, currently 6x tests!):
``` ```
@ -79,3 +87,13 @@ that a new major release of LLVM is required.
Those channels are only used to test and fix builds in advance. They may be Those channels are only used to test and fix builds in advance. They may be
broken at times and must not delay stable channel updates. broken at times and must not delay stable channel updates.
# Testing
Useful tests:
- Version: chrome://version/
- GPU acceleration: chrome://gpu/
- Essential functionality: Browsing, extensions, video+audio, JS, ...
- WebGL: https://get.webgl.org/
- VA-API: https://wiki.archlinux.org/index.php/chromium#Hardware_video_acceleration
- Optional: Widevine CDM (proprietary), Benchmarks, Ozone, etc.