| /external/python/setuptools/docs/development/ |
| D | releases.rst | 5 In order to allow for rapid, predictable releases, Setuptools uses a
6 mechanical technique for releases, enacted on tagged commits by
18 uses a mechanical release process, it's very easy to make releases whenever the
22 While some find the frequent releases somewhat surprising, they only empower
23 the user. Although releases are made frequently, users can choose the frequency
24 at which they use those releases. If instead Setuptools contributions were only
26 those official releases were made. With frequent releases, the user can govern
29 Frequent releases also then obviate the need for dev or beta releases in most
30 cases. Because releases are made early and often, bugs are discovered and
37 releases.
|
| /external/python/google-api-python-client/docs/dyn/ |
| D | firebaserules_v1.projects.releases.html | 75 …1.projects.html">projects</a> . <a href="firebaserules_v1.projects.releases.html">releases</a></h1>
82 …releases/prod -> projects/foo/rulesets/uuid123 * projects/foo/releases/prod/beta -> projects/foo/r…
109 …releases/prod -> projects/foo/rulesets/uuid123 * projects/foo/releases/prod/beta -> projects…
118 "name": "A String", # Format: `projects/{project_id}/releases/{release_id}`
133 "name": "A String", # Format: `projects/{project_id}/releases/{release_id}`
144 …source name for the `Release` to delete. Format: `projects/{project_id}/releases/{release_id}` (re…
162 …name: string, Required. Resource name of the `Release`. Format: `projects/{project_id}/releases/{r…
173 "name": "A String", # Format: `projects/{project_id}/releases/{release_id}`
184 …name: string, Required. Resource name of the `Release`. Format: `projects/{project_id}/releases/{r…
214 …releases/prod -> projects/foo/rulesets/uuid1234 * projects/foo/releases/prod/v1 -> projects/…
[all …]
|
| /external/deqp/external/vulkancts/doc/ |
| D | vulkan-cts-withdrawal-2019-03.txt | 4 to withdraw Vulkan CTS 1.1.0.x releases.
6 These releases are being discontinued due to improved quality and coverage
7 provided by more recent releases. Once the releases are withdrawn it will not be
8 possible to make conformance submissions against these releases.
10 The Khronos Group recommends updating to Vulkan CTS 1.1.3.x and more recent releases
28 2019-09-05 The affected releases are withdrawn.
|
| D | vulkan-cts-withdrawal-2020-10.txt | 4 to withdraw Vulkan CTS 1.2.0.x releases.
6 These releases are being discontinued due to improved quality and coverage
7 provided by more recent releases. Once the releases are withdrawn it will not be
8 possible to make conformance submissions against these releases.
10 The Khronos Group recommends updating to Vulkan CTS 1.2.4.x and more recent releases
30 2021-04-01 The affected releases are withdrawn.
|
| D | vulkan-cts-withdrawal-2021-09.txt | 4 to withdraw Vulkan CTS 1.2.4.x releases.
6 These releases are being discontinued due to improved quality and coverage
7 provided by more recent releases. Once the releases are withdrawn it will not be
8 possible to make conformance submissions against these releases.
10 The Khronos Group recommends updating to Vulkan CTS 1.2.7.x and more recent releases
29 2022-03-27 The affected releases are withdrawn.
|
| D | vulkan-cts-withdrawal-2021-01.txt | 4 to withdraw Vulkan CTS 1.2.1.x releases.
6 These releases are being discontinued due to improved quality and coverage
7 provided by more recent releases. Once the releases are withdrawn it will not be
8 possible to make conformance submissions against these releases.
10 The Khronos Group recommends updating to Vulkan CTS 1.2.5.x and more recent releases
30 2021-07-16 The affected releases are withdrawn.
|
| D | vulkan-cts-withdrawal-2020-07.txt | 4 to withdraw Vulkan CTS 1.1.5.x releases.
6 These releases are being discontinued due to improved quality and coverage
7 provided by more recent releases. Once the releases are withdrawn it will not be
8 possible to make conformance submissions against these releases.
10 The Khronos Group recommends updating to Vulkan CTS 1.2.3.x and more recent releases
30 2021-01-19 The affected releases are withdrawn.
|
| D | vulkan-cts-withdrawal-2021-03.txt | 4 to withdraw Vulkan CTS 1.2.2.x releases.
6 These releases are being discontinued due to improved quality and coverage
7 provided by more recent releases. Once the releases are withdrawn it will not be
8 possible to make conformance submissions against these releases.
10 The Khronos Group recommends updating to Vulkan CTS 1.2.5.x and more recent releases
30 2021-08-22 The affected releases are withdrawn.
|
| D | vulkan-cts-withdrawal-2020-03.txt | 4 to withdraw Vulkan CTS 1.1.4.x releases.
6 These releases are being discontinued due to improved quality and coverage
7 provided by more recent releases. Once the releases are withdrawn it will not be
8 possible to make conformance submissions against these releases.
10 The Khronos Group recommends updating to Vulkan CTS 1.2.2.x and more recent releases
31 2020-10-14 The affected releases are withdrawn.
|
| D | vulkan-cts-withdrawal-2020-01.txt | 4 to withdraw Vulkan CTS 1.1.3.x releases.
6 These releases are being discontinued due to improved quality and coverage
7 provided by more recent releases. Once the releases are withdrawn it will not be
8 possible to make conformance submissions against these releases.
10 The Khronos Group recommends updating to Vulkan CTS 1.2.1.x and more recent releases
31 2020-07-29 The affected releases are withdrawn.
|
| D | vulkan-cts-withdrawal-2020-10-2.txt | 4 to withdraw Vulkan CTS 1.1.6.x releases.
6 These releases are being discontinued due to improved quality and coverage
7 provided by more recent releases. Once the releases are withdrawn it will not be
8 possible to make conformance submissions against these releases.
10 The Khronos Group recommends updating to Vulkan CTS 1.2.4.x and more recent releases
31 2021-04-22 The affected releases are withdrawn.
|
| D | vulkan-cts-withdrawal-2019-04.txt | 4 to withdraw Vulkan CTS 1.1.1.x releases.
6 These releases are being discontinued due to improved quality and coverage
7 provided by more recent releases. Once the releases are withdrawn it will not be
8 possible to make conformance submissions against these releases.
10 The Khronos Group recommends updating to Vulkan CTS 1.1.3.x and more recent releases
31 2019-10-10 The affected releases are withdrawn.
|
| D | vulkan-cts-withdrawal-2021-07.txt | 4 to withdraw Vulkan CTS 1.2.3.x releases.
6 These releases are being discontinued due to improved quality and coverage
7 provided by more recent releases. Once the releases are withdrawn it will not be
8 possible to make conformance submissions against these releases.
10 The Khronos Group recommends updating to Vulkan CTS 1.2.6.x and more recent releases
31 2022-01-05 The affected releases are withdrawn.
|
| D | vulkan-cts-withdrawal-2019-09.txt | 4 to withdraw Vulkan CTS 1.1.2.x releases.
6 These releases are being discontinued due to improved quality and coverage
7 provided by more recent releases. Once the releases are withdrawn it will not be
8 possible to make conformance submissions against these releases.
10 The Khronos Group recommends updating to Vulkan CTS 1.1.5.x and more recent releases
31 2020-03-08 The affected releases are withdrawn.
|
| D | vulkan-cts-withdrawal-2018-09.txt | 4 to withdraw Vulkan CTS 1.0.2.x releases.
6 These releases are being discontinued due to improved quality and coverage
7 provided by more recent releases. Once the releases are withdrawn it will not be
8 possible to make conformance submissions against these releases.
10 The Khronos Group recommends updating to Vulkan CTS 1.1.0.x and more recent releases
34 2019-03-13 The affected releases are withdrawn.
|
| D | vulkan-cts-withdrawal-2017-11.txt | 4 to withdraw Vulkan CTS 1.0.0.x and Vulkan CTS 1.0.1.x releases.
6 These releases are being discontinued due to improved quality and coverage
7 provided by more recent releases. Once the releases are withdrawn it will not be
8 possible to make conformance submissions against these releases.
35 2018-05-15 The affected releases are withdrawn.
|
| /external/catch2/scripts/ |
| D | extractFeaturesFromReleaseNotes.py | 38 def link_to_changes_in_release(release, releases): argument
43 :param releases: A container of releases, in descending order - newest to oldest
48 if release == releases[-1]:
51 index = releases.index(release)
52 previous_release = releases[index + 1]
60 releases = []
70 releases.append(release_name)
81 print(link_to_changes_in_release(current_version, releases))
|
| /external/rust/crates/grpcio-sys/grpc/bazel/ |
| D | update_mirror.sh | 60 upload github.com/bazelbuild/bazel/releases/download/1.0.0/bazel-1.0.0-linux-x86_64
61 upload github.com/bazelbuild/bazel/releases/download/1.0.0/bazel-1.0.0-darwin-x86_64
62 upload github.com/bazelbuild/bazel/releases/download/1.0.0/bazel-1.0.0-windows-x86_64.exe
64 upload github.com/bazelbuild/bazel/releases/download/2.2.0/bazel-2.2.0-linux-x86_64
65 upload github.com/bazelbuild/bazel/releases/download/2.2.0/bazel-2.2.0-darwin-x86_64
66 upload github.com/bazelbuild/bazel/releases/download/2.2.0/bazel-2.2.0-windows-x86_64.exe
68 upload github.com/bazelbuild/bazel/releases/download/3.7.1/bazel-3.7.1-linux-x86_64
69 upload github.com/bazelbuild/bazel/releases/download/3.7.1/bazel-3.7.1-darwin-x86_64
70 upload github.com/bazelbuild/bazel/releases/download/3.7.1/bazel-3.7.1-windows-x86_64.exe
|
| /external/python/google-api-python-client/googleapiclient/discovery_cache/documents/ |
| D | firebaserules.v1.json | 148 "releases": { object
151 …releases/prod -> projects/foo/rulesets/uuid123 * projects/foo/releases/prod/beta -> projects/foo/r…
152 "flatPath": "v1/projects/{projectsId}/releases",
154 "id": "firebaserules.projects.releases.create",
167 "path": "v1/{+name}/releases",
181 "flatPath": "v1/projects/{projectsId}/releases/{releasesId}",
183 "id": "firebaserules.projects.releases.delete",
189 … Resource name for the `Release` to delete. Format: `projects/{project_id}/releases/{release_id}`",
191 "pattern": "^projects/[^/]+/releases/.*$",
207 "flatPath": "v1/projects/{projectsId}/releases/{releasesId}",
[all …]
|
| /external/tpm2-tss/ |
| D | RELEASE.md | 5 Our releases will follow the semantic versioning scheme.
11 * C is the 'micro' version, incremented for bug fix releases
38 Git supports GPG signed tags and for releases after the `1.1.0` release will have tags signed by a …
50 ## Hosting Releases on Github
51 Github automagically generates a page in their UI that maps git tags to 'releases' (even if the tag…
55 …post a signed release to Github here: https://wiki.debian.org/Creating%20signed%20GitHub%20releases
79 Release candidates and proper releases should be announced on the 01.org TPM2 mailing list: https:/…
83 The most recent minor releases will receive bug fixes and bug fix releases.
87 The project aims for 3 releases per year; early spring, summer, late fall.
|
| /external/wayland/ |
| D | releasing.txt | 32 For Wayland official and point releases, also publish the publican
40 For x.y.0 releases, indicate the schedule for the x.y+1.0
46 5. Update releases.html in wayland-web with links to tarballs and
50 snippet that can be pasted into releases.html (or e.g. in emacs
56 $ git commit ./releases.html -m "releases: Add ${RELEASE_NUMBER} release"
60 For x.y.0 releases, also create the release series x.y branch. The x.y
62 and is where we create x.y.z releases from. Creating the x.y branch
|
| /external/selinux/scripts/ |
| D | release | 16 DEST="releases/$RELEASE_TAG"
56 echo "Add the following to the $WIKIDIR/Releases.md wiki page:"
64 echo "[Release Notes](https://github.com/SELinuxProject/selinux/releases/download/$RELEASE_TAG/RELE…
66 echo "[full log](https://github.com/SELinuxProject/selinux/releases/download/$RELEASE_TAG/log-$RELE…
68 echo "[short log](https://github.com/SELinuxProject/selinux/releases/download/$RELEASE_TAG/shortlog…
76 …echo -n "[$tarball](https://github.com/SELinuxProject/selinux/releases/download/$RELEASE_TAG/$tarb…
85 echo -n "[selinux-${RELEASE_TAG}.tar.gz](https://github.com/SELinuxProject/selinux/releases/downloa…
103 echo "Add files from releases/$RELEASE_TAG as assets to the new github release"
|
| /external/skia/ |
| D | WORKSPACE.bazel | 34 …"https://mirror.bazel.build/github.com/bazelbuild/bazel-skylib/releases/download/1.1.1/bazel-skyli…
35 … "https://github.com/bazelbuild/bazel-skylib/releases/download/1.1.1/bazel-skylib-1.1.1.tar.gz",
47 …"https://mirror.bazel.build/github.com/bazelbuild/rules_python/releases/download/0.5.0/rules_pytho…
48 … "https://github.com/bazelbuild/rules_python/releases/download/0.5.0/rules_python-0.5.0.tar.gz",
59 …"https://mirror.bazel.build/github.com/bazelbuild/rules_go/releases/download/v0.29.0/rules_go-v0.2…
60 "https://github.com/bazelbuild/rules_go/releases/download/v0.29.0/rules_go-v0.29.0.zip",
68 …"https://mirror.bazel.build/github.com/bazelbuild/bazel-gazelle/releases/download/v0.24.0/bazel-ga…
69 …"https://github.com/bazelbuild/bazel-gazelle/releases/download/v0.24.0/bazel-gazelle-v0.24.0.tar.g…
|
| /external/perfetto/docs/contributing/ |
| D | sdk-releasing.md | 18 release (cherry-picks on the releases/vN.x branch).
28 git push origin origin/master:refs/heads/releases/v16.x
30 git checkout -b releases/v16.x -t origin/releases/v16.x
41 git checkout -b releases/v16.x -t origin/releases/v16.x
117 # Should print: Your branch is up to date with 'origin/releases/v16.x'.
118 # Do NOT proceed if your branch has diverged from origin/releases/vX.X
147 9. Open https://github.com/google/perfetto/releases/new and
|
| /external/icu/libandroidicu/include/unicode/ |
| D | uvernum.h | 53 * This value will change in the subsequent releases of ICU
60 * This value will change in the subsequent releases of ICU
66 * This value will change in the subsequent releases of ICU
72 * This value will change in the subsequent releases of ICU
86 * This value will change in the subsequent releases of ICU
100 * This value will change in the subsequent releases of ICU.
139 * This value will change in the subsequent releases of ICU
146 * This value will change in subsequent releases of ICU.
174 * This value may change in subsequent releases of ICU.
183 * This value may change in subsequent releases of ICU.
|