tools/git-repo.git/docs/release-process.md, branch v2.14.1

switch to "main" branch for development

2020-11-16T05:07:33+00:00

We're migrating from "master" to "main" as the default development branch. This only affects repo itself, not manifests. Change-Id: I27489dd721c9a467a1c43736808cb3b3c1365433 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/288082 Reviewed-by: Michael Mortensen Tested-by: Mike Frysinger

release-process: document schedule (including freezes) publicly

2020-07-23T08:07:38+00:00

Change-Id: Ic037b54630017740d7859292b32b8c57f4af7854 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/274772 Tested-by: Mike Frysinger Reviewed-by: Jonathan Nieder

init: rename --repo-branch to --repo-rev

2020-03-18T00:24:43+00:00

We refer to this as "revision" in help text, and in REPO_REV envvar, so rename to --repo-rev to be consistent. We keep --repo-branch for backwards compatibility, but as a hidden option. Bug: https://crbug.com/gerrit/11045 Change-Id: I1ecc282fba32917ed78a63850360c08469db849a Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/259352 Tested-by: Mike Frysinger Reviewed-by: David Pursehouse

docs: document git/python/Ubuntu/Debian release schedules

2020-02-12T00:27:59+00:00

Going purely on upstream package release cycles doesn't tell the whole story: a lot of people run LTS distros which will have older versions of software we want to support. Build out a table for us to quickly reference when making decisions as to what versions of git/python we want to support, and when we can drop them. This will also help to refer users to as why we made a specific decision that might be affecting them. Change-Id: I7aea24bbefd50e358aeacf11e8c15a346c8fb8a9 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/254572 Tested-by: Mike Frysinger Reviewed-by: David Pursehouse

docs: start a release document

2019-06-13T03:18:10+00:00

Change-Id: I884639665c020338ec9ceeb1add5c3b862583674