From b90c7cd8f9e14418c4a486f424fc9afc84d3ff18 Mon Sep 17 00:00:00 2001 From: Brian Gan Date: Wed, 28 Oct 2026 20:02:40 +0000 Subject: [PATCH] docs: add Repology links for distro package versions The Ubuntu and Debian release wiki pages added in https://gerrit-review.googlesource.com/c/git-repo/+/649983 only list distro release and EOL dates, not which versions of Python, Git, or OpenSSH shipped in each distro release. Add Repology package version links alongside the distro release pages in python-support.md and requirements.json so maintainers can check which versions shipped across historical Ubuntu and Debian releases. Bug: 575551885 Change-Id: Ib256fd9b364074b52d3e15d185af519d8376cb28 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/650868 Reviewed-by: Gavin Mak Tested-by: Brian Gan Commit-Queue: Brian Gan --- docs/python-support.md | 9 +++++---- requirements.json | 9 ++++++--- 2 files changed, 11 insertions(+), 7 deletions(-) diff --git a/docs/python-support.md b/docs/python-support.md index ba75f28d9..87d37e627 100644 --- a/docs/python-support.md +++ b/docs/python-support.md @@ -45,10 +45,10 @@ that are critical to us. That said, let's assume we need functionality that only exists in Python 3.7. How do we decide when it's acceptable to drop Python 3.6? -1. Review what major distros are using the previous version of Python, and - when they go EOL (e.g. via [Ubuntu releases] & [Debian releases]). - Generally we care about Ubuntu LTS & current/previous Debian stable - versions. +1. Review what major distros are using the previous version of Python (e.g. + via [Repology Python versions]), and when they go EOL (e.g. via + [Ubuntu releases] & [Debian releases]). Generally we care about Ubuntu LTS + & current/previous Debian stable versions. * If they're all EOL already, then go for it, drop support. * If they aren't EOL, start a thread on [repo-discuss] to see how the user base feels about the proposal. @@ -89,6 +89,7 @@ $ repo-2.32 init --repo-rev=repo-1 ... [repo-discuss]: https://groups.google.com/forum/#!forum/repo-discuss [Debian releases]: https://wiki.debian.org/DebianReleases#Versions_of_Debian_stable +[Repology Python versions]: https://repology.org/project/python/versions [repo hooks]: ./repo-hooks.md [repo launcher]: ../repo [Ubuntu releases]: https://wiki.ubuntu.com/Releases diff --git a/requirements.json b/requirements.json index 513a02c54..d19b66bc6 100644 --- a/requirements.json +++ b/requirements.json @@ -19,11 +19,14 @@ # Hard versions are when we refuse to work the tool. Users will be shown an # error message before we abort entirely. -# When deciding whether to upgrade a version requirement, check out what versions -# major distros (e.g. Ubuntu LTS & Debian stable) ship to see who will be -# impacted: +# When deciding whether to upgrade a version requirement, check out what +# versions major distros (e.g. Ubuntu LTS & Debian stable) ship and when they +# go EOL to see who will be impacted: # https://wiki.ubuntu.com/Releases # https://wiki.debian.org/DebianReleases#Versions_of_Debian_stable +# https://repology.org/project/python/versions +# https://repology.org/project/git/versions +# https://repology.org/project/openssh/versions { # The repo launcher itself. This allows us to force people to upgrade as some