From d1e93dd58a6bc74b9a6f872bb3a7a0123e8a9933 Mon Sep 17 00:00:00 2001 From: Mike Frysinger Date: Thu, 10 Oct 2019 18:34:39 -0400 Subject: [PATCH] python-support: adjust major versions The plan previously documented was <=1.13.x is Python 2 and >=1.14.x is Python 3. Other projects that migrated Python versions and drop support for older have tended to take a more drastic version jump to make it clearer to users. So lets adjust the plan to say <=1.x will support Python 2, and >=2.x will be Python 3-only. This also allows us to harmonize the repo launcher version. It is currently sitting at v1.26 and has been incremented independently of the repo version for the life of the project. While we might know these lower nuances, pretty much no one else does and it just leads to confusion: do I know version 1.26 or version 1.13.7? Or do I have both? What does that even mean? Once we update the major version to 2.0.0, we can also adjust the launcher script to 2.0.0, and then the launcher release process will be tied to a new repo release in general. Bug: https://crbug.com/gerrit/10418 Change-Id: Idb2257371a06e56d2923cf717345c028f49176a2 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/240372 Reviewed-by: David Pursehouse Tested-by: Mike Frysinger --- docs/python-support.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/python-support.md b/docs/python-support.md index 35806de..a5c490a 100644 --- a/docs/python-support.md +++ b/docs/python-support.md @@ -7,9 +7,9 @@ their old LTS/corp systems and have little power to change the system. ## Summary -* Python 3.6 (released Dec 2016) is required by default starting with repo-1.14. +* Python 3.6 (released Dec 2016) is required by default starting with repo-2.x. * Older versions of Python (e.g. v2.7) may use the legacy feature-frozen branch - based on repo-1.13. + based on repo-1.x. ## Overview