summaryrefslogtreecommitdiffstats
path: root/docs/repo-hooks.md
diff options
context:
space:
mode:
authorMike Frysinger <vapier@google.com>2020-02-11 18:43:34 -0500
committerMike Frysinger <vapier@google.com>2020-02-12 00:27:59 +0000
commit3645bd24200b0f97eaeb8f65552ec67cc5a3fce8 (patch)
treeb74ffb690a75668a980de53e7a4490d12caea07f /docs/repo-hooks.md
parent5f2b04519596f285cc70717c95231ce85666e382 (diff)
downloadgit-repo-3645bd24200b0f97eaeb8f65552ec67cc5a3fce8.tar.gz
docs: document git/python/Ubuntu/Debian release schedules
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 <vapier@google.com> Reviewed-by: David Pursehouse <dpursehouse@collab.net>
Diffstat (limited to 'docs/repo-hooks.md')
0 files changed, 0 insertions, 0 deletions