Use legacy[milestone#] as channel name for old milestones

Don't want builds on old (but not too old) milestones to fail,
so set channel to legacy instead of failing for milestones whose
major version difference with canary is > 3 and < 10.

Change-Id: If67493cf8613812c24e666aa6e8d9c8615e7a2d5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/2816145
Reviewed-by: Michael Moss <mmoss@chromium.org>
Commit-Queue: Michael Moss <mmoss@chromium.org>
Auto-Submit: Chong Gu <chonggu@google.com>
2 files changed
tree: 7978cccc813f54bbae4b371cddfe290edee9980c
  1. infra/
  2. recipes/
  3. scripts/
  4. site_config/
  5. .gitattributes
  6. .gitignore
  7. .style.yapf
  8. .vpython
  9. .yapfignore
  10. codereview.settings
  11. CROS_OWNERS
  12. DEPS
  13. environment.cfg.py
  14. LICENSE
  15. OWNERS
  16. PRESUBMIT.py
  17. README.md
  18. WATCHLISTS
README.md

Recipes

If you're here to make a change to ‘recipes’ (the code located in scripts/slave/recipes*), please take a look at the README for more information pertaining to recipes.

Style

The preferred style is PEP8 with two-space indent; that is, the Chromium Python style. Functions use lowercase_with_underscores, with the exception of the special functions RunSteps and RunTests in recipes. Use yapf (git cl format --no-clang-format) to autoformat new code.