releases (full) in projects: third_party

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:releases (Results 1 – 25 of 1844) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...74

/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/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/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/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/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 v3.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 ![point releases of stable](../doc-assets/lws-relpol-4.svg) 106 backport it to a few recent releases, not just the last one. This is pretty`
/third_party/ltp/testcases/open_posix_testsuite/Documentation/
D	HOWTO_Tagging	`4 Releases of the POSIX Test Suite will happen at defined (TBD) intervals. 5 In order to get code included in the releases, the tagging scheme below 31 threads, semaphores, message queues, timers). M<1 is for releases before 34 N = Minor release. The various minor releases have yet to be determined,`
/third_party/toybox/www/
D	faq.html	8 <li><h2><a href="#releases">Why time based releases?</a></h2></li> 52 Apache license. Similarly, Apple froze xcode at the last GPLv2 releases 83 potentially being upgraded to new software releases.</p> 105 <h2><a name="releases" />Q: Why time based releases?</h2> 106 <p>A: Toybox targets quarterly releases (a similar schedule to the Linux 111 <p>Releases provide synchronization points where the developers certify 115 Releases focus end-user testing on specific versions 117 Releases also force the developers to do periodic tidying, packaging, 125 Releases give you the option to schedule upgrades later, and not to rock 145 <p>As for why releases on a schedule are better than releases "when it's
/third_party/skia/
D	WORKSPACE.bazel	`25 …# From https://github.com/llvm/llvm-project/releases/download/llvmorg-13.0.0/clang+llvm-13.0.0-x86… 28 …clang_url = "https://github.com/llvm/llvm-project/releases/download/llvmorg-13.0.0/clang+llvm-13.0… 38 … "https://github.com/bazelbuild/bazel-skylib/releases/download/1.1.1/bazel-skylib-1.1.1.tar.gz", 39 …"https://mirror.bazel.build/github.com/bazelbuild/bazel-skylib/releases/download/1.1.1/bazel-skyli…`
/third_party/exfat-utils/
D	.travis_get_mainline_kernel	`8 wget https://www.kernel.org/releases.json 10 echo "Could not download kernel.org/releases.json" 14 VER=$(cat releases.json \| python2.7 -c "import sys, json; print json.load(sys.stdin)['latest_stable…`
/third_party/node/doc/guides/
D	releases.md	37 * [LTS releases](#lts-releases) 38 * [Major releases](#major-releases) 55 to create a nightly release for the current HEAD if public test releases are 88 releases. Additionally for releases, this file is signed by the individual 194 command. (For semver-minor releases, make sure to remove the `semver-minor` tag 309 releases in each major release line. A link to the new release needs to be added 352 For security releases, begin the commit message with the phrase 482 `release-type` is either "Current" or "LTS". For LTS releases, you should also 575 # Checking for releases ... 604 b. Log in to the server via SSH and check for releases that can be promoted, [all …]
/third_party/skia/third_party/externals/abseil-cpp/
D	README.md	`14 - [Releases](#releases) 116 ## Releases section in Abseil - C++ Common Libraries 121 Releases](https://github.com/abseil/abseil-cpp/releases) to which we backport 123 management](https://abseil.io/about/releases) document for more details.`
/third_party/boost/boost/interprocess/sync/
D	named_upgradable_mutex.hpp	108 //!Effects: The calling thread releases the exclusive ownership of the mutex. 136 //!Effects: The calling thread releases the sharable ownership of the mutex. 164 //!Effects: The calling thread releases the upgradable ownership of the mutex. 171 //!Effects: The thread atomically releases exclusive ownership and acquires 177 //!Effects: The thread atomically releases exclusive ownership and acquires 183 //!Effects: The thread atomically releases upgradable ownership and acquires 191 //!Effects: The thread atomically releases upgradable ownership and acquires 198 //!Effects: The thread atomically releases upgradable ownership and tries to 206 //!Effects: The thread atomically releases upgradable ownership and tries to acquire 215 //!Effects: The thread atomically releases sharable ownership and tries to acquire [all …]
/third_party/boost/libs/outcome/doc/html/
D	changelog.html	18 …tps-github-com-ned14-outcome-releases-tag-v2-1-4">v2.1.4 ??? (Boost 1.74) <a href="https://github.… 23 …thub-com-ned14-outcome-releases-tag-v2-1-3">v2.1.3 29th April 2020 (Boost 1.73) <a href="https://g… 28 …ub-com-ned14-outcome-releases-tag-v2-1-2">v2.1.2 11th December 2019 (Boost 1.72) <a href="https://… 33 …hub-com-ned14-outcome-releases-tag-v2-1-1">v2.1.1 19th August 2019 (Boost 1.71) <a href="https://g… 38 …-github-com-ned14-outcome-releases-tag-v2-1">v2.1 12th Apr 2019 (Boost 1.70) <a href="https://gith… 39 …thub-com-ned14-outcome-releases-tag-v2-0-boost-peer-review">v2.0 18th Jan 2018 <a href="https://gi… 47 …tps-github-com-ned14-outcome-releases-tag-v2-1-4">v2.1.4 ??? (Boost 1.74) <a href="https://github.… 117 …thub-com-ned14-outcome-releases-tag-v2-1-3">v2.1.3 29th April 2020 (Boost 1.73) <a href="https://g… 177 …ub-com-ned14-outcome-releases-tag-v2-1-2">v2.1.2 11th December 2019 (Boost 1.72) <a href="https://… 249 …hub-com-ned14-outcome-releases-tag-v2-1-1">v2.1.1 19th August 2019 (Boost 1.71) <a href="https://g… [all …]
/third_party/python/Doc/faq/
D	general.rst	132 information about bugfix releases. 134 Not all releases are bugfix releases. In the run-up to a new major release, a 135 series of development releases are made, denoted as alpha, beta, or release 136 candidate. Alphas are early releases in which interfaces aren't yet finalized; 137 it's not unexpected to see an interface change between two alpha releases. 209 Announcements of new software releases and events can be found in 221 Alpha and beta releases are available from https://www.python.org/downloads/. All 222 releases are announced on the comp.lang.python and comp.lang.python.announce 298 Very stable. New, stable releases have been coming out roughly every 6 to 18 302 The developers issue "bugfix" releases of older versions, so the stability of [all …]
/third_party/flutter/skia/third_party/externals/angle2/doc/
D	ChoosingANGLEBranch.md	`4 tag specific revisions as releases, which may make the process of choosing a 33 In order to determine which branches are used by Chromium releases, please use 35 information about current Chromium releases. Find the entry for a suitable 36 release channel (for now, we recommend one of the Windows desktop releases), and`
/third_party/boost/boost/interprocess/sync/shm/
D	named_upgradable_mutex.hpp	108 //!Effects: The calling thread releases the exclusive ownership of the mutex. 136 //!Effects: The calling thread releases the sharable ownership of the mutex. 164 //!Effects: The calling thread releases the upgradable ownership of the mutex. 171 //!Effects: The thread atomically releases exclusive ownership and acquires 177 //!Effects: The thread atomically releases exclusive ownership and acquires 183 //!Effects: The thread atomically releases upgradable ownership and acquires 191 //!Effects: The thread atomically releases upgradable ownership and acquires 198 //!Effects: The thread atomically releases upgradable ownership and tries to 206 //!Effects: The thread atomically releases upgradable ownership and tries to acquire 215 //!Effects: The thread atomically releases sharable ownership and tries to acquire
/third_party/skia/third_party/externals/oboe/docs/
D	ChangeLog.md	`3 This changelog is deprecated. See the [Oboe releases page](https://github.com/google/oboe/relea… 5 ## [1.0.0](https://github.com/google/oboe/releases/tag/1.0.0)`
/third_party/skia/third_party/externals/angle2/doc/
D	ChoosingANGLEBranch.md	`4 tag specific revisions as releases, which may make the process of choosing a 33 In order to determine which branches are used by Chromium releases, please use 35 information about current Chromium releases. Find the entry for a suitable 36 release channel (for now, we recommend one of the Windows desktop releases), and`
/third_party/flutter/flutter/dev/bots/
D	unpublish_package.dart	8 /// releases are available. 25 const String releaseFolder = '/releases'; 245 …final List<Map<String, String>> releases = jsonData['releases'].map<Map<String, String>>((dynamic … 249 final Map<Channel, Map<String, String>> paths = await _getArchivePaths(releases); 250 …releases.removeWhere((Map<String, String> value) => revisionsBeingRemoved.contains(value['hash']) … 251 releases.sort((Map<String, String> a, Map<String, String> b) { 256 jsonData['releases'] = releases; 262 …final Map<String, String> replacementRelease = releases.firstWhere((Map<String, String> value) => … 276 …Future<Map<Channel, Map<String, String>>> _getArchivePaths(List<Map<String, String>> releases) asy… 279 for (Map<String, String> revision in releases) {

12 3 4 5 6 7 8 9 10 >>...74