Home
last modified time | relevance | path

Searched +full:create +full:- +full:release (Results 1 – 25 of 1055) sorted by relevance

12345678910>>...43

/third_party/node/doc/contributing/
Dreleases-node-api.md1 # Node.js Node-API version release process
3 This document describes the technical aspects of the Node.js Node-API version
4 release process.
8 * [How to create a release](#how-to-create-a-release)
9 * [0. Pre-release steps](#0-pre-release-steps)
10 * [1. Update the main branch](#1-update-the-main-branch)
11 * [2. Create a new branch for the release](#2-create-a-new-branch-for-the-release)
12 * [3. Update `NODE_API_SUPPORTED_VERSION_MAX`](#3-update-node_api_supported_version_max)
13 * [4. Define `addon_context_register_func`](#4-define-addon_context_register_func)
14 * [5. Update version guards](#5-update-version-guards)
[all …]
Dreleases.md1 # Node.js release process
3 This document describes the technical aspects of the Node.js release process.
5 Technical Steering Committee (TSC) to create, promote, and sign
6 official release builds for Node.js, hosted on <https://nodejs.org/>.
10 * [Who can make a release?](#who-can-make-a-release)
11 * [1. Jenkins release access](#1-jenkins-release-access)
12 * [2. \<nodejs.org> access](#2-nodejsorg-access)
13 * [3. A publicly listed GPG key](#3-a-publicly-listed-gpg-key)
14 * [How to create a release](#how-to-create-a-release)
15 * [0. Pre-release steps](#0-pre-release-steps)
[all …]
Dsecurity-release-process.md1 # Security release process
3 The security release process covers the steps required to plan/implement a
4 security release. This document is copied into the description of the Next
5 Security Release and used to track progress on the release. It contains _**TEXT
6 LIKE THIS**_ which will be replaced during the release process with the
9 ## Security release stewards
11 For each security release, a security steward will take ownership for
17 [security steward on/off boarding](security-steward-on-off-boarding.md).
20 [README.md](https://github.com/nodejs/node#security-release-stewards).
22 | Company | Person | Release Date |
[all …]
/third_party/rust/crates/clap/.github/workflows/
Dpost-release.yml1 name: post-release
5 - "v*"
10 create-release:
12 contents: write # for actions/create-release to create a release
13 name: create-release
14 runs-on: ubuntu-latest
16 upload_url: ${{ steps.release.outputs.upload_url }}
19 - name: Get the release version from the tag
23 …# See: https://github.community/t5/GitHub-Actions/How-to-get-just-the-tag-name/m-p/32167/highlight…
26 - name: Checkout repository
[all …]
/third_party/icu/docs/processes/release/tasks/publish/
Dindex.md1 ---
4 parent: Release & Milestone Tasks
7 ---
9 <!--
12 -->
18 {: .no_toc .text-delta }
23 ---
25 ## Create a release branch in GitHub
27 Once the branch is created, only changes necessary for the target release are
30 ---
[all …]
/third_party/skia/third_party/externals/tint/tools/src/cmd/roll-release/
Dmain.go7 // http://www.apache.org/licenses/LICENSE-2.0
15 // roll-release is a tool to roll changes in Tint release branches into Dawn,
16 // and create new Tint release branches.
37 "github.com/go-git/go-git/v5"
38 "github.com/go-git/go-git/v5/config"
39 "github.com/go-git/go-git/v5/plumbing"
40 "github.com/go-git/go-git/v5/plumbing/transport"
41 git_http "github.com/go-git/go-git/v5/plumbing/transport/http"
42 "github.com/go-git/go-git/v5/storage/memory"
46 toolName = "roll-release"
[all …]
/third_party/skia/third_party/externals/angle2/doc/
DBranchingAndRolling.md6 describes how to update that dependency, and, if necessary, create an ANGLE
7 branch to correspond to a branched release of Chrome.
9 ANGLE's commit queue also runs browser-level tests which are hosted in
10 the Chromium repository. To reduce the chance of a Chromium-side
18 the Chromium roll into ANGLE. All of the ANGLE-related autorollers are
20 documentation](../infra/ANGLEWrangling.md#the-auto-rollers).
24 Chromium's dependency on third-party projects is tracked in [the Chromium
30 * Change the [git SHA-1 revision
31 number](http://git-scm.com/book/ch6-1.html) to be that of the commit
32 on which Chromium should depend. Please use the full SHA-1, not a
[all …]
/third_party/protobuf/
DCONTRIBUTING.md10 github, please read [How to create github pull requests](https://help.github.com/articles/about-pul…
21 … need to sign an [individual CLA](https://cla.developers.google.com/about/google-individual?csw=1).
23 …then you'll need to sign a [corporate CLA](https://cla.developers.google.com/about/google-corporat…
35 included in the next major/minor version release (e.g., 3.6.0 release). If you
36 need to include a bug fix in a patch release (e.g., 3.5.2), make sure it’s
37 already merged to master, and then create a pull request cherry-picking the
38 commits from master branch to the release branch (e.g., branch 3.5.x).
44 our response time within 7-days but if you don’t get any response in a few
51 the final release.
55 * If you are a Googler, it is preferable to first create an internal CL and
[all …]
/third_party/icu/docs/processes/release/tasks/
Ddocs.md1 ---
4 parent: Release & Milestone Tasks
7 ---
9 <!--
12 -->
18 {: .no_toc .text-delta }
23 ---
30 see** [ICU-8862](https://unicode-org.atlassian.net/browse/ICU-8862) **).**
33 `sudo apt-get install doxygen`
36 1. To update Doxygen, first [download binary or source release
[all …]
Dmiscellaneous.md1 ---
4 parent: Release & Milestone Tasks
7 ---
9 <!--
12 -->
18 {: .no_toc .text-delta }
23 ---
30 ---
44 ---
46 ## Release ticket
[all …]
/third_party/notofonts/.github/workflows/
Dmonthly-release.yaml1 name: Monthly release/tag
4 - cron: '0 0 1 * *'
9 runs-on: ubuntu-latest
12 - name: Checkout branch
15 - name: Generate release tag
17 uses: amitsingh-007/next-release-tag@v3.0.0
20 tag_prefix: 'noto-monthly-release-'
22 - name: Create Release
23 uses: actions/create-release@v1
28 release_name: Noto Monthly Release ${{ steps.generate_release_tag.outputs.release_tag }}
[all …]
/third_party/rust/crates/codespan/
DCONTRIBUTING.md5 - [Introduction](#introduction)
6 - [Code of Conduct](#code-of-conduct)
7 - [Matrix Room](#matrix-room)
8 - [Reporting Bugs and Suggesting Improvements](#reporting-bugs-and-suggesting-improvements)
9 - [Contribution Workflow](#contribution-workflow)
10 - [Quality Standards](#quality-standards)
11 - [Release Process](#release-process)
30 Joining the matrix room at [#codespan:matrix.org][codespan-matrix] is a good way to get in touch wi…
32 [codespan-matrix]: https://app.element.io/#/room/#codespan:matrix.org
36 Bugs (unwanted behaviour) and suggested improvements are tracked as [GitHub issues][github-issues].
[all …]
/third_party/astc-encoder/Docs/
DBuilding.md17 To use CMake you must first configure the build. Create a build directory in
22 # Create a build directory
28 # x86-64 using a Visual Studio solution
29 cmake -G "Visual Studio 16 2019" -T ClangCL -DCMAKE_INSTALL_PREFIX=..\ ^
30 -DASTCENC_ISA_AVX2=ON -DASTCENC_ISA_SSE41=ON -DASTCENC_ISA_SSE2=ON ..
32 # x86-64 using NMake
33 cmake -G "NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=..\ ^
34 -DASTCENC_ISA_AVX2=ON -DASTCENC_ISA_SSE41=ON -DASTCENC_ISA_SSE2=ON ..
42 Using the Visual Studio Clang-CL LLVM toolchain (`-T ClangCL`) is optional but
66 To use CMake you must first configure the build. Create a build directory
[all …]
/third_party/benchmark/docs/
Dreleasing.md1 # How to release
5 * `parallel -j0 exec ::: test/*_test` can help ensure everything at least
7 * Prepare release notes
8 * `git log $(git describe --abbrev=0 --tags)..HEAD` gives you the list of
11 * Create one last commit that updates the version saved in `CMakeLists.txt`, `MODULE.bazel`
13 release version you're creating. (This version will be used if benchmark is installed
29 __version__ = "1.8.0" # <-- change this to the release version you are creating
34 * Create a release through github's interface
35 * Note this will create a lightweight tag.
37 * `git pull --tags`
[all …]
/third_party/ninja/
DRELEASING.md1 Notes to myself on all the steps to make for a Ninja release.
3 ### Push new release branch:
4 1. Run afl-fuzz for a day or so and run ninja_test
5 2. Consider sending a heads-up to the ninja-build mailing list first
6 3. Make sure branches 'master' and 'release' are synced up locally
9 git commit -am 'mark this 1.5.0.git'
11 5. git checkout release; git merge master
13 7. Fix version in doc/manual.asciidoc (exists only on release branch)
14 8. commit, tag, push (don't forget to push --tags)
16 git commit -am v1.5.0; git push origin release
[all …]
/third_party/protobuf/cmake/
DREADME.md6 and optionally [Git](http://git-scm.com) installed on your computer before proceeding.
27 Create a folder where protobuf headers/libraries/binaries will be installed after built:
44 You can get the latest stable source packages from the release page:
48 For example: if you only need C++, download `protobuf-cpp-[VERSION].tar.gz`; if
49 you need C++ and Java, download `protobuf-java-[VERSION].tar.gz` (every package
51 download `protobuf-all-[VERSION].tar.gz`.
55 C:\Path\to> git clone -b [release_tag] https://github.com/protocolbuffers/protobuf.git
57 Where *[release_tag]* is a git tag like *v3.0.0-beta-1* or a branch name like *master*
66 step if you are using a release .tar.gz or .zip package):
69 C:\Path\to\protobuf> git submodule update --init --recursive
[all …]
/third_party/libdrm/
DRELEASING1 The release criteria for libdrm is essentially "if you need a release,
2 make one". There is no designated release engineer or maintainer.
3 Anybody is free to make a release if there's a certain feature or bug
6 When new ioctl definitions are merged into drm-next, we will add
7 support to libdrm, at which point we typically create a new release.
10 Follow these steps to release a new version of libdrm:
16 2) Run `ninja -C builddir/ dist` to generate the tarballs.
18 builddir/meson-dist/ matches the number you bumped to. Move that
19 tarball to the libdrm repo root for the release script to pick up.
27 4) Use the release.sh script from the xorg/util/modular repo to
[all …]
/third_party/jinja2/.github/workflows/
Dpublish.yaml5 - '*'
8 runs-on: ubuntu-latest
12 - uses: actions/checkout@ac593985615ec2ede58e132d2e21d2b1cbd6127c
13 - uses: actions/setup-python@5ccb29d8773c3f3f653e1705f474dfaa8a06a912
15 python-version: '3.x'
17 cache-dependency-path: 'requirements/*.txt'
18 - run: pip install -r requirements/build.txt
20 - run: echo "SOURCE_DATE_EPOCH=$(git log -1 --pretty=%ct)" >> $GITHUB_ENV
21 - run: python -m build
23 - name: generate hash
[all …]
/third_party/skia/third_party/externals/d3d12allocator/src/
DD3D12Sample.cpp2 // Copyright (c) 2019-2020 Advanced Micro Devices, Inc. All rights reserved.
135 wprintf(L"Allocate Size=%llu Alignment=%llu -> %p\n", Size, Alignment, memory); in CustomAllocate()
146 --g_CpuAllocationCount; in CustomFree()
201 …// the command queue since it has not reached the "g_CommandQueue->Signal(g_Fences, g_FenceValues)… in WaitForFrame()
202 if (g_Fences[frameIndex]->GetCompletedValue() < g_FenceValues[frameIndex]) in WaitForFrame()
204 …// we have the g_Fences create an event which is signaled once the g_Fences's current value is "g_… in WaitForFrame()
205 … CHECK_HR( g_Fences[frameIndex]->SetEventOnCompletion(g_FenceValues[frameIndex], g_FenceEvent) ); in WaitForFrame()
216 CHECK_HR( g_CommandQueue->Signal(g_Fences[frameIndex], g_FenceValues[frameIndex]) ); in WaitGPUIdle()
227 // PURPOSE, MERCHANTABILITY, OR NON-INFRINGEMENT.
230 // Row-by-row memcpy
[all …]
/third_party/lzma/CPP/Windows/
DSynchronization.h32 …WRes Create(bool manualReset, bool initiallyOwn, LPCTSTR name = NULL, LPSECURITY_ATTRIBUTES sa = N…
57 WRes Create(bool initiallyOwn = false)
70 return CBaseEvent::Create(true, initiallyOwn, name); in CreateWithName()
78 WRes Create() in Create() function
104 WRes Create(bool initiallyOwn, LPCTSTR name = NULL, LPSECURITY_ATTRIBUTES sa = NULL)
120 WRes Release()
130 CMutexLock(CMutex &object): _object(&object) { _object->Lock(); }
131 ~CMutexLock() { _object->Release(); }
152 WRes Create(UInt32 initCount, UInt32 maxCount) in Create() function
160 WRes Release() { return Semaphore_Release1(&_object); } in Release() function
[all …]
/third_party/protobuf/objectivec/
DGPBUnknownFieldSet.m1 // Protocol Buffers - Google's data interchange format
3 // https://developers.google.com/protocol-buffers/
60 [copied release];
65 // protos can turn on -Wdirect-ivar-access without issues.
67 #pragma clang diagnostic ignored "-Wdirect-ivar-access"
69 - (id)copyWithZone:(NSZone *)zone {
77 - (void)dealloc {
84 - (BOOL)isEqual:(id)object {
88 if ((fields_ == NULL) && (set->fields_ == NULL)) {
90 } else if ((fields_ != NULL) && (set->fields_ != NULL)) {
[all …]
/third_party/libfuse/dev-docs/
Drelease-process.md1 Release Process
4 * `set TAG fuse-A.B.C`
9 * When creating new minor release:
10 …* Create signing key for the next release: `P=fuse-<A.B+1> signify-openbsd -G -n -p signify/$P.pub…
12 * Expire old release signing keys (keep one around just in case)
13 * Update authors: `git log --all --pretty="format:%an <%aE>" | sort -u >> AUTHORS`
14 * `git commit --all -m "Released $TAG"`
15 * `git tag -s $TAG`
18 * `cd fuse-x.y.z`
22 * `(cd build; python3 -m pytest test/)`
[all …]
/third_party/gn/src/base/mac/
Dscoped_typeref.h2 // Use of this source code is governed by a BSD-style license that can be
15 // of a reference to any type that is maintained by Retain and Release methods.
17 // The Traits structure must provide the Retain and Release methods for type T.
29 // static void Release(CGLContextObj object) { CGLContextRelease(object); }
32 // For the many types that have pass-by-pointer create functions, the function
43 // it should not assume this ownership and must create its own (by calling
83 Traits::Release(object_); in ~ScopedTypeRef()
92 // by pass-by-pointer create functions. To enforce this, require that the
105 Traits::Release(object_);
123 // ScopedTypeRef<>::release() is like std::unique_ptr<>::release. It is NOT
[all …]
/third_party/skia/third_party/externals/angle2/src/tests/gl_tests/
DImageTestMetal.mm3 // Use of this source code is governed by a BSD-style license that can be
41 release();
54 release();
63 release();
73 release();
85 release();
93 void release()
96 [mSurface release];
147 " texcoord.y = 1.0 - texcoord.y;\n"
177 eglQueryDisplayAttribEXT(getEGLWindow()->getDisplay(), EGL_DEVICE_EXT, &angleDevice));
[all …]
/third_party/benchmark/.github/workflows/
Dbuild-and-test.yml1 name: build-and-test
8 # TODO: add 32-bit builds (g++ and clang++) for ubuntu
9 # (requires g++-multilib and libc6:i386)
14 runs-on: ${{ matrix.os }}
16 fail-fast: false
18 os: [ubuntu-latest, ubuntu-20.04, macos-latest]
19 build_type: ['Release', 'Debug']
22 - displayTargetName: windows-latest-release
23 os: windows-latest
24 build_type: 'Release'
[all …]

12345678910>>...43