Searched refs:releases (Results 1 – 25 of 591) sorted by relevance
12345678910>>...24
5 In order to allow for rapid, predictable releases, Setuptools uses a6 mechanical technique for releases, enacted by Travis following a29 uses a mechanical release process, it's very easy to make releases whenever the33 While some find the frequent releases somewhat surprising, they only empower34 the user. Although releases are made frequently, users can choose the frequency35 at which they use those releases. If instead Setuptools contributions were only37 those official releases were made. With frequent releases, the user can govern40 Frequent releases also then obviate the need for dev or beta releases in most41 cases. Because releases are made early and often, bugs are discovered and48 releases.
4 to withdraw Vulkan CTS 1.0.2.x releases.6 These releases are being discontinued due to improved quality and coverage7 provided by more recent releases. Once the releases are withdrawn it will not be8 possible to make conformance submissions against these releases.10 The Khronos Group recommends updating to Vulkan CTS 1.1.0.x and more recent releases34 2019-03-13 The affected releases are withdrawn.
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 coverage7 provided by more recent releases. Once the releases are withdrawn it will not be8 possible to make conformance submissions against these releases.35 2018-05-15 The affected releases are withdrawn.
14 Release notes for previous releases can be found on15 `the Download Page <https://releases.llvm.org/download.html>`_.24 documentation <https://llvm.org/docs/ReleaseNotes.html>`_. All LLVM releases may25 be downloaded from the `LLVM releases web site <https://llvm.org/releases/>`_.33 see the `releases page <https://llvm.org/releases/>`_.
13 - Add to https://svn.xiph.org/releases/opus/24 Releases are commited to https://svn.xiph.org/releases/opus/35 Binary releases are copied manually to42 For major releases, recreate the files on https://opus-codec.org/examples/
68 releases = ['2.6.1' , '2.6.18-smp-220.0' ] variable in kernel_versions_test74 for v in self.releases:81 for v in self.releases + self.candidates:
23 Unlike earlier releases, ICU4C 2.8 supports historical time zone29 Olson: ftp://ftp.iana.org/tz/releases/34 For ICU releases >= 2.8, both ICU4C and ICU4J implement full52 Index of ftp://ftp.iana.org/tz/releases/71 $ wget "ftp://ftp.iana.org/tz/releases/tzdata*.tar.gz"
19 wget https://github.com/bazelbuild/buildtools/releases/download/0.4.5/buildifier24 wget https://github.com/bazelbuild/buildtools/releases/download/0.4.5/buildozer
178 releases = [args.release]181 releases = client_matrix.get_release_tags(lang)191 releases = [args.release]194 for release in releases:198 'All docker images built for %s at %s.' % (lang, releases),
33 This is an end-to-end update test of Chrome OS releases. Given a test57 (e.g. it is in gs://chromeos-releases/).66 artifacts (e.g. it is in gs://chromeos-releases).71 You can choose payloads from this bucket: gs://chromeos-releases/73 Sample from gs://chromeos-releases:74 gs://chromeos-releases/dev-channel/samus/9433.0.0/payloads/chromeos_9433.0148 source_payload_uri='gs://chromeos-releases/canary-channel/nami/10760.0151 target_payload_uri='gs://chromeos-releases/canary-channel/nami/10906.0
14 Odd numbered versions (such as 3.3) designate new developmental releases.15 Even numbered versions (such as 3.4) designate stable releases.
12 Odd numbered versions (such as 6.3) designate new developmental releases.13 Even numbered versions (such as 6.2) designate stable releases.
14 Odd numbered versions (such as 6.3) designate new developmental releases.15 Even numbered versions (such as 6.2) designate stable releases.
14 Odd numbered versions (such as 6.1) designate new developmental releases.15 Even numbered versions (such as 6.2.x) designate stable releases.
14 Odd numbered versions (such as 6.1) designate new developmental releases.15 Even numbered versions (such as 6.2) designate stable releases.
5 In order to get code included in the releases, the tagging scheme below31 threads, semaphores, message queues, timers). M<1 is for releases before34 N = Minor release. The various minor releases have yet to be determined,
13 …value: "https://oss.sonatype.org/service/local/repositories/releases/content/com/google/errorprone…17 …value: "https://oss.sonatype.org/service/local/repositories/releases/content/com/google/errorprone…
21 LLVM is released on a time based schedule --- with major releases roughly22 every 6 months. In between major releases there may be dot releases.24 on feedback from the community. Typically, dot releases should be made if28 Unless otherwise stated, dot releases will follow the same procedure as29 major releases.53 The release process will be accelerated for dot releases. If the first round190 * Major releases (X.0): Hans Wennborg191 * Stable releases (X.n): Tom Stellard299 #. For dot releases all patches must maintain both API and ABI compatibility with361 #. Create a new sub-directory ``X.Y`` in the releases directory.[all …]
131 information about bugfix releases.133 Not all releases are bugfix releases. In the run-up to a new major release, a134 series of development releases are made, denoted as alpha, beta, or release135 candidate. Alphas are early releases in which interfaces aren't yet finalized;136 it's not unexpected to see an interface change between two alpha releases.208 Announcements of new software releases and events can be found in220 Alpha and beta releases are available from https://www.python.org/downloads/. All221 releases are announced on the comp.lang.python and comp.lang.python.announce297 Very stable. New, stable releases have been coming out roughly every 6 to 18299 usually around 18 months between major releases.[all …]
131 information about bugfix releases.133 Not all releases are bugfix releases. In the run-up to a new major release, a134 series of development releases are made, denoted as alpha, beta, or release135 candidate. Alphas are early releases in which interfaces aren't yet finalized;136 it's not unexpected to see an interface change between two alpha releases.208 Announcements of new software releases and events can be found in220 Alpha and beta releases are available from https://www.python.org/downloads/. All221 releases are announced on the comp.lang.python and comp.lang.python.announce303 Very stable. New, stable releases have been coming out roughly every 6 to 18305 usually around 18 months between major releases.[all …]
10 prefer the `LLVM 3.8 Release Notes <http://llvm.org/releases/3.8.0/docs20 some of the current users of the code. All LLVM releases may be downloaded21 from the `LLVM releases web site <http://llvm.org/releases/>`_.31 one. To see the release notes for a specific release, please see the `releases32 page <http://llvm.org/releases/>`_.
67 …curl -L -o checkstyle-8.12-all.jar https://github.com/checkstyle/checkstyle/releases/download/chec…72 …https://github.com/google/google-java-format/releases/download/google-java-format-1.5/google-java-…