Searched +full:release +full:- +full:please +full:- +full:- +full:branches +full:- +full:- +full:main (Results 1 – 25 of 167) sorted by relevance
1234567
| /external/pytorch/ |
| D | RELEASE.md | 3 <!-- toc -->
5 - [Release Compatibility Matrix](#release-compatibility-matrix)
6 - [Release Cadence](#release-cadence)
7 - [General Overview](#general-overview)
8 - [Frequently Asked Questions](#frequently-asked-questions)
9 - [Cutting a release branch preparations](#cutting-a-release-branch-preparations)
10 - [Cutting release branches](#cutting-release-branches)
11 - [`pytorch/pytorch`](#pytorchpytorch)
12 - [`pytorch/builder` / PyTorch domain libraries](#pytorchbuilder--pytorch-domain-libraries)
13 …- [Making release branch specific changes for PyTorch](#making-release-branch-specific-changes-for…
[all …]
|
| D | SECURITY.md | 3 - [**Reporting a Vulnerability**](#reporting-a-vulnerability)
4 - [**Using Pytorch Securely**](#using-pytorch-securely)
5 - [Untrusted models](#untrusted-models)
6 - [Untrusted inputs](#untrusted-inputs)
7 - [Data privacy](#data-privacy)
8 - [Using distributed features](#using-distributed-features)
9 - [**CI/CD security principles**](#cicd-security-principles)
12 Beware that none of the topics under [Using Pytorch Securely](#using-pytorch-securely) are consider…
16 Please report security issues using https://github.com/pytorch/pytorch/security/advisories/new
18 Please refer to the following page for our responsible disclosure policy, reward guidelines, and th…
[all …]
|
| /external/angle/doc/ |
| D | BranchingAndRolling.md | 4 uses (i.e. depends upon) other third-party software that comes from different repositories. ANGLE s…
5 …r repositories in the [ANGLE DEPS file](https://chromium.googlesource.com/angle/angle/+/main/DEPS).
11 to correspond to a branched release of Chrome.
13 ANGLE's commit queue also runs browser-level tests which are hosted in
14 the Chromium repository. To reduce the chance of a Chromium-side
23 All of the ANGLE-related autorollers are documented in the [ANGLE Wrangling documentation](../infra…
31 …* Change the [git SHA-1 revision number](http://git-scm.com/book/ch6-1.html) to be that of the com…
32 on which to depend upon (Note: use the full SHA-1, not a
34 * You can find the SHA-1 for a particular commit with `git log` on the appropriate branch of the
37 wish to view from the list on the left-hand side, and then click on the "tree" link at the top of
[all …]
|
| /external/google-cloud-java/.github/workflows/ |
| D | versions.yaml | 7 # http://www.apache.org/licenses/LICENSE-2.0
18 branches:
19 - main
23 unmanaged-versions-check:
24 runs-on: ubuntu-latest
26 - uses: actions/checkout@v3
27 - run: ./generation/check_non_release_please_versions.sh
29 # For Release Please pull requests, the artifacts being published must not
31 existing-versions-check:
32 runs-on: ubuntu-latest
[all …]
|
| /external/webrtc/docs/native-code/development/ |
| D | index.md | 4 iOS. See the [Android][webrtc-android-development] and [iOS][webrtc-ios-development]
10 First, be sure to install the [prerequisite software][webrtc-prerequisite-sw].
12 [webrtc-prerequisite-sw]: https://webrtc.googlesource.com/src/+/main/docs/native-code/development/p…
22 $ mkdir webrtc-checkout
23 $ cd webrtc-checkout
24 $ fetch --nohooks webrtc
36 2. Optionally you can specify how new branches should be tracked:
43 3. Alternatively, you can create new local branches like this (recommended):
47 $ git checkout main
48 $ git new-branch your-branch-name
[all …]
|
| /external/libwebsockets/READMEs/ |
| D | README.release-policy.md | 1 # lws release policy
10 The stable releases go on to a branch like v4.0-stable as described below, over
13 v4.0.0 but build into your planning that you will need to follow v4.0-stable in
16 And we only backport fixes to the last stable release, although we will make
19 should build into your planning that you will follow lws release upgrades.
21 If you find problems and create fixes, please upstream them, simplifying your
33 
35 If you have patches (you are a hero) they should be targeted at `main`.
42 $ git fetch https://libwebsockets.org/repo/libwebsockets +main:m && git reset --hard m
46 local checkout to exactly match `m`. This replaces your checked-out tree
[all …]
|
| /external/AFLplusplus/ |
| D | README.md | 3 <img align="right" src="https://raw.githubusercontent.com/AFLplusplus/Website/main/static/aflpp_bg.…
5 Release version: [4.10c](https://github.com/AFLplusplus/AFLplusplus/releases)
14 * Marc "van Hauser" Heuse <mh@mh-sec.de>
17 * Heiko "hexcoder-" Eissfeldt <heiko.eissfeldt@hexco.de>
23 AFL++ is a superior fork to Google's AFL - more speed, more and better
27 terms of the Apache-2.0 License. See the [LICENSE](LICENSE) for details.
34 please visit [docs/README.md](docs/README.md).
39 [branches](#branches). The best branches to use are, however, `stable` or
40 `dev` - depending on your risk appetite. Also take a look at the list of
47 `afl-clang-fast` with `AFL_LLVM_CMPLOG=1`. You can find the `aflplusplus`
[all …]
|
| /external/mesa3d/docs/ |
| D | submittingpatches.rst | 7 ----------------
9 - Patches should not mix code changes with code formatting changes
11 - Code patches should follow Mesa :doc:`coding
13 - Whenever possible, patches should only affect individual Mesa/Gallium
15 - Patches should never introduce build breaks and should be bisectable
17 - Patches should be properly :ref:`formatted <formatting>`.
18 - Patches should be sufficiently :ref:`tested <testing>` before
20 - Patches should be :ref:`submitted <submit>` via a merge request for
26 ----------------
28 - Lines should be limited to 75 characters or less so that Git logs
[all …]
|
| /external/pytorch/.github/scripts/ |
| D | generate_ci_workflows.py | 29 # For use to enable workflows to run on pytorch/pytorch-canary
36 def __post_init__(self) -> None:
60 branches: str = "nightly" variable in BinaryBuildWorkflow
63 macos_runner: str = "macos-14-xlarge"
66 def __post_init__(self) -> None:
69 f"{self.os}-binary-{self.package_type}-{self.abi_version}"
72 self.build_environment = f"{self.os}-binary-{self.package_type}"
75 self.build_environment += "-split"
77 def generate_workflow_file(self, workflow_template: jinja2.Template) -> None:
80 / f"workflows/generated-{self.build_environment}-{self.branches}.yml"
[all …]
|
| /external/mbedtls/ |
| D | CONTRIBUTING.md | 7 -----------------------------------
10 - [Sign-off](#license-and-copyright): all commits must be signed off.
11 - [Tests](#tests): please ensure the PR includes adequate tests.
12 - [Changelog](#documentation): if needed, please provide a changelog entry.
13 - [Backports](#long-term-support-branches): provide a backport if needed (it's fine to wait until t…
16 ----------------
17 - Contributions should include tests, as mentioned in the [Tests](#tests) and [Continuous Integrati…
18 - The code should be written in a clean and readable style, and must follow [our coding standards](…
19 - The code should be written in a portable generic way, that will benefit the whole community, and …
20 - The code should be secure, and will be reviewed from a security point of view as well.
[all …]
|
| /external/openthread/third_party/mbedtls/repo/ |
| D | CONTRIBUTING.md | 7 -----------------------------------
10 - [Sign-off](#license-and-copyright): all commits must be signed off.
11 - [Tests](#tests): please ensure the PR includes adequate tests.
12 - [Changelog](#documentation): if needed, please provide a changelog entry.
13 - [Backports](#long-term-support-branches): provide a backport if needed (it's fine to wait until t…
16 ----------------
17 - Contributions should include tests, as mentioned in the [Tests](#tests) and [Continuous Integrati…
18 - The code should be written in a clean and readable style, and must follow [our coding standards](…
19 - The code should be written in a portable generic way, that will benefit the whole community, and …
20 - The code should be secure, and will be reviewed from a security point of view as well.
[all …]
|
| /external/executorch/.github/workflows/ |
| D | lint.yml | 5 branches-ignore:
6 - nightly
8 branches:
9 - main
10 - release/*
14 …p: ${{ github.workflow }}-${{ github.event.pull_request.number || github.sha }}-${{ github.event_n…
15 cancel-in-progress: true
19 uses: pytorch/test-infra/.github/workflows/linux_job.yml@release/2.5
22 docker-image: executorch-ubuntu-22.04-linter
23 fetch-depth: 0
[all …]
|
| /external/pytorch/.github/workflows/ |
| D | lint.yml | 5 branches-ignore:
6 - nightly
8 branches:
9 - main
10 - release/*
11 - landchecks/*
14 permissions: read-all
18 lintrunner-clang:
19 uses: pytorch/test-infra/.github/workflows/linux_job.yml@release/2.4
23 docker-image: pytorch-linux-jammy-cuda11.8-cudnn9-py3.9-linter
[all …]
|
| /external/zxing/.github/workflows/ |
| D | codeql-analysis.yml | 8 # We have attempted to detect the languages in your repository. Please check
17 branches: [ master ]
19 # The branches below must be a subset of the branches above
20 branches: [ master ]
22 - cron: '42 6 * * 1'
27 runs-on: ubuntu-latest
30 fail-fast: false
35 …hub.com/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#…
38 - name: Checkout repository
42 - name: Initialize CodeQL
[all …]
|
| /external/pcre/.github/workflows/ |
| D | codeql.yml | 8 # We have attempted to detect the languages in your repository. Please check
16 branches: [ master ]
18 # The branches below must be a subset of the branches above
19 branches: [ master ]
21 - cron: '27 6 * * 4'
24 permissions: read-all
29 runs-on: ubuntu-latest
33 security-events: write
36 fail-fast: false
40 # Learn more about CodeQL language support at https://git.io/codeql-language-support
[all …]
|
| /external/libcap-ng/.github/workflows/ |
| D | codeql-analysis.yml | 8 # We have attempted to detect the languages in your repository. Please check
16 branches: [ master ]
18 # The branches below must be a subset of the branches above
19 branches: [ master ]
21 - cron: '35 12 * * 4'
26 runs-on: ubuntu-latest
30 fail-fast: false
35 …en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/configurin…
38 - name: Checkout repository
41 - name: get envinronment info
[all …]
|
| /external/rust/android-crates-io/crates/grpcio-sys/grpc/third_party/opencensus-proto/ |
| D | RELEASING.md | 1 # How to Create a Release of OpenCensus Proto (for Maintainers Only)
5 We re-generate gen-go files and deploy jars to Maven Central under the following systems:
7 - Ubuntu 14.04
11 ## Release Go files
13 To generate the Go files from protos, you'll need to install protoc, protoc-gen-go and grpc-gateway…
14 Follow the instructions [here](http://google.github.io/proto-lens/installing-protoc.html),
15 …com/golang/protobuf#installation) and [here](https://github.com/grpc-ecosystem/grpc-gateway#instal…
17 Then run the following commands to re-generate the gen-go files:
20 $ cd $(go env GOPATH)/src/github.com/census-instrumentation/opencensus-proto
21 $ git checkout -b update-gen-go
[all …]
|
| /external/skia/site/docs/dev/tools/ |
| D | codesearch.md | 2 ---
6 ---
16 Skia tree. Chromium code search provides cross-references.
20 main [skia](http://cs/#skia/skia/) repo, internal Code Search indexes the
23 cross-references and code analysis are not available.
26 [skia-buildbot](https://github.com/google/skia-buildbot) repos are useful for
27 investigating history and blame, or for exploring release branches or other
28 branches. However, the search functionality is fairly limited, cross-references
36 Code search option |Search |XRef |History |Repos |Branches |Freshness
37 …--------------------|-------|-----|--------|------------------------------|---------|-------------…
[all …]
|
| /external/armnn/scripts/ |
| D | get_compute_library.sh | 3 # Copyright © 2018-2023 Arm Ltd. All rights reserved.
4 # SPDX-License-Identifier: MIT
10 #DEFAULT_CLFRAMEWORKREVISION="branches/arm_compute_23_02" # Release 23.02
13 …97398e4b0" #9454: Implement CL kernel for a native batched matmul Quantized - LHS transposed, RHS …
16 …echo -e "get_compute_library.sh: Clones the Arm Compute Library (ACL) repo from the ML Platform se…
20 regularly updated by the Arm NN team on the Arm NN 'main' branch.
21 …During release periods, the ACL pin will point to an ACL release branch which exists on the ML Pla…
22 …The repo directory will be named 'clframework' unless defined by the '-n' argument to this script.…
24 echo "Usage: $CMD -s <CLFRAMEWORK_SHA>"
25 echo "Usage: $CMD -p (Print current default clframework SHA)"
[all …]
|
| /external/llvm/docs/ |
| D | DeveloperPolicy.rst | 28 policies <copyright-license-patents>` with contributors to the project.
31 contributing one-off patches can do so in an informal way by sending them to the
32 `llvm-commits mailing list
33 <http://lists.llvm.org/mailman/listinfo/llvm-commits>`_ and engaging another
40 always welcome `one-off patches`_ from people who do not routinely contribute to
47 -------------
50 the projects you are interested in, such as `llvm-dev
51 <http://lists.llvm.org/mailman/listinfo/llvm-dev>`_ for LLVM, `cfe-dev
52 <http://lists.llvm.org/mailman/listinfo/cfe-dev>`_ for Clang, or `lldb-dev
53 <http://lists.llvm.org/mailman/listinfo/lldb-dev>`_ for LLDB. If you are
[all …]
|
| D | HowToReleaseLLVM.rst | 2 How To Release LLVM To The Public
12 This document contains information about successfully releasing LLVM ---
13 including subprojects: e.g., ``clang`` and ``dragonegg`` --- to the public. It
14 is the Release Manager's responsibility to ensure that a high quality build of
17 If you're looking for the document on how to test the release candidates and
18 create the binary packages, please refer to the :doc:`ReleaseProcess` instead.
22 Release Timeline
25 LLVM is released on a time based schedule --- with major releases roughly
27 The release manager will determine if and when to make a dot release based
29 there are large number of bug-fixes in the stable branch or a critical bug
[all …]
|
| /external/opencensus-java/ |
| D | RELEASING.md | 1 # How to Create a Release of OpenCensus Java (for Maintainers Only)
7 - Ubuntu 14.04
18 - Follow the instructions on [this
19 page](http://central.sonatype.org/pages/ossrh-guide.html) to set up an
21 - You only need to create the account, not set up a new project
22 - Contact a OpenCensus Java maintainer to add your account after you
24 - (For release deployment only) [Install
25 GnuPG](http://central.sonatype.org/pages/working-with-pgp-signatures.html#installing-gnupg)
27 pair](http://central.sonatype.org/pages/working-with-pgp-signatures.html#generating-a-key-pair).
29 …key](http://central.sonatype.org/pages/working-with-pgp-signatures.html#distributing-your-public-k…
[all …]
|
| /external/toolchain-utils/llvm_tools/ |
| D | git_llvm_rev.py | 3 # Use of this source code is governed by a BSD-style license that can be
9 r1234 is parsed as '(main, 1234)'.
20 MAIN_BRANCH = "main"
30 # llvm-svn: 375505
38 # The first element is the first non-`llvm-svn` commit that exists. Later ones
50 # - |dir| is the directory of the LLVM checkout
51 # - |remote| is the name of the LLVM remote. Generally it's "origin".
61 def parse(rev: str) -> "Rev":
70 # (main, r${commits_since_base_commit}).
83 def __str__(self) -> str:
[all …]
|
| /external/robolectric/ |
| D | README.md | 1 …src="https://rawgithub.com/robolectric/robolectric/master/images/robolectric-horizontal.png"/>](ht…
4 [](ht…
6 …-standard unit testing framework for Android. With Robolectric, your tests run in a simulated Andr…
31 …oject, extend its functionality, and join the community of contributors, please visit [robolectric…
37 … [Maven](https://github.com/robolectric/deckard-maven) or [Gradle](https://github.com/robolectric/…
48 Robolectric is built using Gradle. Both Android Studio and IntelliJ can import the top-level `build…
51 [this guide](https://robolectric.org/building-robolectric/).
53 To get a high-level overview of Robolectric's architecture, check out
59 this GitHub repository, which is considered the *source-of-truth* for
62 internally at Google, where contributions from first-party Android developers
[all …]
|
| /external/gflags/ |
| D | README.md | 1 [](https://travis-ci.org/gfla…
8 ----------------
12 This maintenance release improves lives of Bazel users (no more "config.h" leaking into global incl…
18 Please report any further issues with this release using the GitHub issue tracker.
22 ------------
26 This maintenance release primarily fixes build issues on Windows and
29 Please report any further issues with this release using the GitHub issue tracker.
33 ----------------
37 This release adds support for use of the gflags library as external dependency
39 or [pkg-config](https://www.freedesktop.org/wiki/Software/pkg-config/).
[all …]
|
1234567