
Upstream makes standalone releases of zipflinger with its own
versioning scheme, but they do not make tags with those versions.  And
upstream does not document how they make releases.  So we have to do a
lot of guesswork when looking for the source that matches a given
release number.  The best we've been able to come up with is to build
a given tag, then compare it to the official releases on
https://maven.google.com to see which it most closely matches.

For example, Debian's v7.2.2 was built from:
https://android.googlesource.com/platform/tools/base/+archive/refs/tags/studio-2021.2.1-patch2/zipflinger.tar.gz

Going forward, there are some promising candidates for tags to use:

* platform-tools-29.0.1
* platform-tools-29.0.2
* platform-tools-29.0.3
* platform-tools-29.0.4
* platform-tools-29.0.5
* platform-tools-29.0.6
* platform-tools-30.0.0
* platform-tools-30.0.1
* platform-tools-30.0.2
* platform-tools-30.0.3
* platform-tools-30.0.4
* platform-tools-30.0.5
* platform-tools-31.0.0
* platform-tools-31.0.1
* platform-tools-31.0.2
* platform-tools-31.0.3
* platform-tools-32.0.0
* platform-tools-33.0.0
* platform-tools-33.0.1
* platform-tools-33.0.2
* platform-tools-33.0.3

* studio-1.4
* studio-1.5
* studio-2.0
* studio-2.0-rc1
* studio-2.2
* studio-2.2-preview3
* studio-2.2.2
* studio-2.3
* studio-2020.3.1
* studio-2021.1.1
* studio-2021.2.1
* studio-2021.2.1-patch1
* studio-2021.2.1-patch2
* studio-2021.3.1-beta
* studio-2022.1.1-canary
* studio-3.0
* studio-3.1.2
* studio-3.2.1
* studio-3.4.0
* studio-4.0.0
* studio-4.1.0
* studio-4.1.1
* studio-4.2.0

 -- Hans-Christoph Steiner <hans@eds.org>, Wed, 14 Sep 2022 15:42:00 +0200
