/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/catch2/scripts/ |
D | extractFeaturesFromReleaseNotes.py | 38 def link_to_changes_in_release(release, releases): argument 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/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-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-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-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-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-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-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-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-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/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/llvm-project/openmp/docs/ |
D | ReleaseNotes.rst | 8 Release notes for previous releases can be found on 9 `the Download Page <https://releases.llvm.org/download.html>`_. 17 from the previous release. All openmp releases may be downloaded 18 from the `LLVM releases web site <https://llvm.org/releases/>`_.
|
/external/llvm-project/lld/docs/ |
D | ReleaseNotes.rst | 10 Release notes for previous releases can be found on 11 `the Download Page <https://releases.llvm.org/download.html>`_. 18 from the previous release. All lld releases may be downloaded 19 from the `LLVM releases web site <https://llvm.org/releases/>`_.
|
/external/virglrenderer/docs/ |
D | release.txt | 2 * This document explain how releases are made and how you can create one locally 6 Since version 0.8.0 releases are now done by means of tags, i.e. the maintainer adds a tag, 8 For more details about GitLab release, see https://docs.gitlab.com/ee/user/project/releases/ 11 or meson release (https://mesonbuild.com/Creating-releases.html)
|
/external/llvm-project/openmp/runtime/tools/lib/ |
D | Uname.pm | 258 my @releases = grep( $_ ne "/etc/lsb-release", bsd_glob( "/etc/*-release" ) ); 261 if ( grep( $_ eq "/etc/fedora-release", @releases ) ) { 262 @releases = grep( $_ ne "/etc/redhat-release", @releases ); 264 if ( @releases == 1 ) { 265 $release = $releases[ 0 ]; 267 if ( @releases == 0 ) { 276 … warning( "More than one release files found in \"/etc/\" directory:", @releases );
|
/external/rust/crates/env_logger/ |
D | CHANGELOG.md | 1 Changes to this crate are tracked via [GitHub Releases][releases]. 3 [releases]: https://github.com/env-logger-rs/env_logger/releases
|
/external/dagger2/ |
D | CHANGELOG.md | 4 - For Dagger 2 releases, please see https://github.com/google/dagger/releases 5 - For Dagger 1 (`ObjectGraph`) releases, see
|
/external/llvm-project/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/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/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/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/>`_.
|