| /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>
115 projects/foo/releases/prod | projects/foo/rulesets/uuid123
116 projects/foo/releases/prod/beta | projects/foo/rulesets/uuid123
117 projects/foo/releases/prod/v23 | projects/foo/rulesets/uuid456
120 `prod/beta` releases refer to the same `Ruleset`. However, `prod/v23`
151 # Environments | releases/qa | releases/qa
152 # Apps | releases/app1_qa | releases/app1/qa
153 # Versions | releases/app1_v2_qa | releases/app1/v2/qa
160 # Format: `projects/{project_id}/releases/{release_id}`
193 # Environments | releases/qa | releases/qa
[all …]
|
| D | androidpublisher_v3.edits.tracks.html | 104 …"releases": [ # A list of all active releases in this track during a read request. On an update re…
108 …tain all versions you wish to be active, including those you wish to retain from previous releases.
145 …"releases": [ # A list of all active releases in this track during a read request. On an update re…
149 …tain all versions you wish to be active, including those you wish to retain from previous releases.
185 …"releases": [ # A list of all active releases in this track during a read request. On an update re…
189 …tain all versions you wish to be active, including those you wish to retain from previous releases.
215 …"releases": [ # A list of all active releases in this track during a read request. On an update re…
219 …tain all versions you wish to be active, including those you wish to retain from previous releases.
253 …"releases": [ # A list of all active releases in this track during a read request. On an update re…
257 …tain all versions you wish to be active, including those you wish to retain from previous releases.
[all …]
|
| /external/python/setuptools/docs/ |
| D | releases.txt | 5 In order to allow for rapid, predictable releases, Setuptools uses a
6 mechanical technique for releases, enacted by Travis following a
29 uses a mechanical release process, it's very easy to make releases whenever the
33 While some find the frequent releases somewhat surprising, they only empower
34 the user. Although releases are made frequently, users can choose the frequency
35 at which they use those releases. If instead Setuptools contributions were only
37 those official releases were made. With frequent releases, the user can govern
40 Frequent releases also then obviate the need for dev or beta releases in most
41 cases. Because releases are made early and often, bugs are discovered and
48 releases.
|
| /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-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-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-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-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-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-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-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-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-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 | 55 upload github.com/bazelbuild/bazel/releases/download/1.0.0/bazel-1.0.0-linux-x86_64
56 upload github.com/bazelbuild/bazel/releases/download/1.0.0/bazel-1.0.0-darwin-x86_64
57 upload github.com/bazelbuild/bazel/releases/download/1.0.0/bazel-1.0.0-windows-x86_64.exe
59 upload github.com/bazelbuild/bazel/releases/download/2.2.0/bazel-2.2.0-linux-x86_64
60 upload github.com/bazelbuild/bazel/releases/download/2.2.0/bazel-2.2.0-darwin-x86_64
61 upload github.com/bazelbuild/bazel/releases/download/2.2.0/bazel-2.2.0-windows-x86_64.exe
63 upload github.com/bazelbuild/bazel/releases/download/3.7.1/bazel-3.7.1-linux-x86_64
64 upload github.com/bazelbuild/bazel/releases/download/3.7.1/bazel-3.7.1-darwin-x86_64
65 upload github.com/bazelbuild/bazel/releases/download/3.7.1/bazel-3.7.1-windows-x86_64.exe
|
| /external/llvm-project/pstl/docs/ |
| D | ReleaseNotes.rst | 14 Release notes for previous releases can be found on
15 `the Download Page <https://releases.llvm.org/download.html>`_.
25 All LLVM releases may be downloaded from the `LLVM releases web site
26 <https://llvm.org/releases/>`_.
30 To see the release notes for a specific release, please see the `releases
31 page <https://llvm.org/releases/>`_.
|
| /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/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/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
99 # Should print: Your branch is up to date with 'origin/releases/v16.x'.
100 # Do NOT proceed if your branch has diverged from origin/releases/vX.X
|
| /external/selinux/scripts/ |
| D | release | 11 DEST=releases/$RELEASE_TAG
42 echo "Add the following to the $WIKIDIR/Releases.md wiki page:"
50 echo "[Release Notes](https://github.com/SELinuxProject/selinux/releases/download/$RELEASE_TAG/RELE…
52 echo "[full log](https://github.com/SELinuxProject/selinux/releases/download/$RELEASE_TAG/log-$RELE…
54 echo "[short log](https://github.com/SELinuxProject/selinux/releases/download/$RELEASE_TAG/shortlog…
59 echo -n "[$i](https://github.com/SELinuxProject/selinux/releases/download/$RELEASE_TAG/$i) "
78 echo "Add files from releases/$RELEASE_TAG as assets to the new github release"
|
| /external/llvm-project/flang/docs/ |
| D | ReleaseNotes.md | 6 > Release notes for previous releases can be found on [the Download
7 > Page](https://releases.llvm.org/download.html).
17 releases may be downloaded from the [LLVM releases web
18 site](https://llvm.org/releases/).
22 release notes for a specific release, please see the [releases
23 page](https://llvm.org/releases/).
|
| /external/libcxx/docs/ |
| D | ReleaseNotes.rst | 14 Release notes for previous releases can be found on
15 `the Download Page <https://releases.llvm.org/download.html>`_.
24 documentation <https://llvm.org/docs/ReleaseNotes.html>`_. All LLVM releases may
25 be downloaded from the `LLVM releases web site <https://llvm.org/releases/>`_.
33 see the `releases page <https://llvm.org/releases/>`_.
|
| /external/clang/test/CXX/dcl.dcl/dcl.spec/dcl.stc/ |
| D | p2.cpp | 10 …' storage class specifier is not permitted in C++11, and will not be supported in future releases}}
15 …' storage class specifier is not permitted in C++11, and will not be supported in future releases}}
28 …' storage class specifier is not permitted in C++11, and will not be supported in future releases}}
32 …' storage class specifier is not permitted in C++11, and will not be supported in future releases}}
41 …' storage class specifier is not permitted in C++11, and will not be supported in future releases}} in foo()
45 …' storage class specifier is not permitted in C++11, and will not be supported in future releases}} in foo()
49 …' storage class specifier is not permitted in C++11, and will not be supported in future releases}} in foo()
|
| /external/llvm-project/clang/test/CXX/dcl.dcl/dcl.spec/dcl.stc/ |
| D | p2.cpp | 10 …' storage class specifier is not permitted in C++11, and will not be supported in future releases}}
15 …' storage class specifier is not permitted in C++11, and will not be supported in future releases}}
28 …' storage class specifier is not permitted in C++11, and will not be supported in future releases}}
32 …' storage class specifier is not permitted in C++11, and will not be supported in future releases}}
41 …' storage class specifier is not permitted in C++11, and will not be supported in future releases}} in foo()
46 …' storage class specifier is not permitted in C++11, and will not be supported in future releases}} in foo()
50 …' storage class specifier is not permitted in C++11, and will not be supported in future releases}} in foo()
|