Searched full:releases (Results 1 – 25 of 1938) sorted by relevance
12345678910>>...78
| /third_party/flutter/flutter/dev/bots/test/ |
| D | fake_process_manager_test.dart | 29 'gsutil acl get gs://flutter_infra/releases/releases.json': <ProcessResult>[
32 'gsutil cat gs://flutter_infra/releases/releases.json': <ProcessResult>[
51 'gsutil acl get gs://flutter_infra/releases/releases.json': <ProcessResult>[
54 'gsutil cat gs://flutter_infra/releases/releases.json': <ProcessResult>[
68 'gsutil acl get gs://flutter_infra/releases/releases.json': <ProcessResult>[
71 'gsutil cat gs://flutter_infra/releases/releases.json': <ProcessResult>[
85 'gsutil acl get gs://flutter_infra/releases/releases.json': <ProcessResult>[
88 'gsutil cat gs://flutter_infra/releases/releases.json': <ProcessResult>[
|
| /third_party/vk-gl-cts/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-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-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-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-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-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-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-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-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-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.
|
| /third_party/wayland_standard/ |
| 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
|
| /third_party/grpc/doc/ |
| D | grpc_release_schedule.md | 3 …hub.com/grpc/grpc-java/releases), [Go](https://github.com/grpc/grpc-go/releases) and [Core](https:…
5 Releases are scheduled every six weeks on Tuesdays on a best effort basis. In some unavoidable situ…
7 Releases are cut from release branches. For Core and Java repos, the release branch is cut two week…
9 Names of gRPC releases are [here](https://github.com/grpc/grpc/blob/master/doc/g_stands_for.md).
|
| /third_party/flutter/skia/third_party/externals/icu/source/common/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.
121 * This value will change in the subsequent releases of ICU
128 * This value will change in subsequent releases of ICU.
156 * This value may change in subsequent releases of ICU.
165 * This value may change in subsequent releases of ICU.
|
| /third_party/icu/icu4c/source/common/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.
|
| /third_party/node/deps/icu-small/source/common/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.
|
| /third_party/skia/third_party/externals/icu/source/common/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.
|
| /third_party/weston/ |
| D | releasing.md | 42 listing of the most notable changes. For x.y.0 releases, indicate the
48 7. Update `releases.html` in wayland.freedesktop.org with links to tarballs and
49 the release email URL. Copy tarballs produced by `release.sh` to `releases/`.
53 git commit -am "releases: add ${RELEASE_NUMBER} release"
56 For x.y.0 releases, also create the release series x.y branch. The x.y branch
58 create x.y.z releases from. Creating the x.y branch opens up master for new
|
| /third_party/json/doc/mkdocs/docs/home/ |
| D | releases.md | 1 # Releases chapter
7 - [include.zip](https://github.com/nlohmann/json/releases/download/v3.7.3/include.zip) (274 KB)
8 …- [include.zip.asc](https://github.com/nlohmann/json/releases/download/v3.7.3/include.zip.asc) (1 …
9 - [json.hpp](https://github.com/nlohmann/json/releases/download/v3.7.3/json.hpp) (791 KB)
10 - [json.hpp.asc](https://github.com/nlohmann/json/releases/download/v3.7.3/json.hpp.asc) (1 KB)
35 - [include.zip](https://github.com/nlohmann/json/releases/download/v3.7.2/include.zip) (274 KB)
36 …- [include.zip.asc](https://github.com/nlohmann/json/releases/download/v3.7.2/include.zip.asc) (1 …
37 - [json.hpp](https://github.com/nlohmann/json/releases/download/v3.7.2/json.hpp) (791 KB)
38 - [json.hpp.asc](https://github.com/nlohmann/json/releases/download/v3.7.2/json.hpp.asc) (1 KB)
66 - [include.zip](https://github.com/nlohmann/json/releases/download/v3.7.1/include.zip) (273 KB)
[all …]
|
| /third_party/boost/libs/contract/doc/ |
| D | release_notes.qbk | 9 This section contains notes on all releases of this library (from the latest to the oldest).
64 Released [@https://github.com/boostorg/contract/releases/tag/v0.5.0 files].
82 Released [@https://github.com/boostorg/contract/releases/tag/v0.4.1 files].
106 Released [@https://github.com/boostorg/contract/releases/tag/v0.4.0 files].
119 Released [@https://github.com/boostorg/contract/releases/tag/v0.3.490 files].
144 Released [@https://github.com/boostorg/contract/releases/tag/v0.3.469 files].
158 Released [@https://github.com/boostorg/contract/releases/tag/v0.2.190 files].
170 Released [@https://github.com/boostorg/contract/releases/tag/v0.1.126 files].
183 Released [@https://github.com/boostorg/contract/releases/tag/v0.1.55 files].
195 Released [@https://github.com/boostorg/contract/releases/tag/v0.1.50 files].
|
| /third_party/libwebsockets/READMEs/ |
| D | README.release-policy.md | 10 The stable releases go on to a branch like v4.0-stable as described below, over
65 v4.0 version, which will never reach 99 point releases itself, but "earlier"
83 When new stable releases are made, the soname is bumped reflecting the API is
94 ## Stable point releases
97 "point releases". So if the original stable release was "v3.0.0", the point
100 
106 backport it to a few recent releases, not just the last one. This is pretty
|
12345678910>>...78