Skip to content

Add script to cut release branch #2567

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 4 commits into from

Conversation

guangy10
Copy link
Contributor

@guangy10 guangy10 commented Mar 21, 2024

Step 1 of release process: Create a release branch.

The branch is named with release/MAJOR.MINOR.

From executorch root, run ./scripts/release/cut-release-branch.sh will cut a release branch off stable branch (viable/strict) by default. Use GIT_BRANCH_TO_CUT_FROM=main ./scripts/release/cut-release-branch.sh to cut off main branch.

Stack from ghstack (oldest at bottom):

Differential Revision: D55208762

Copy link

pytorch-bot bot commented Mar 21, 2024

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/2567

Note: Links to docs will display an error until the docs builds have been completed.

✅ You can merge normally! (1 Unrelated Failure)

As of commit 3abf850 with merge base ec6b88a (image):

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

This comment was automatically generated by Dr. CI and updates every 15 minutes.

guangy10 added a commit that referenced this pull request Mar 21, 2024
ghstack-source-id: ccc90f9
Pull Request resolved: #2567
@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Mar 21, 2024
@guangy10 guangy10 requested review from huydhn and mergennachin March 21, 2024 18:34
@guangy10
Copy link
Contributor Author

@guangy10 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@huydhn
Copy link
Contributor

huydhn commented Mar 21, 2024

Just FYI, I have create the branch protection rules for release and orig/release https://github.com/pytorch/executorch/settings/branches

Step 1 of release process: Create a release branch.

The branch is named with `release/MAJOR.MINOR`.

From executorch root, run `./scripts/release/cut-release-branch.sh` will cut a release branch off stable branch (`viable/strict`) by default. Use `GIT_BRANCH_TO_CUT_FROM=main ./scripts/release/cut-release-branch.sh` to cut off `main` branch.



Differential Revision: [D55208762](https://our.internmc.facebook.com/intern/diff/D55208762)

[ghstack-poisoned]
Step 1 of release process: Create a release branch.

The branch is named with `release/MAJOR.MINOR`.

From executorch root, run `./scripts/release/cut-release-branch.sh` will cut a release branch off stable branch (`viable/strict`) by default. Use `GIT_BRANCH_TO_CUT_FROM=main ./scripts/release/cut-release-branch.sh` to cut off `main` branch.



Differential Revision: [D55208762](https://our.internmc.facebook.com/intern/diff/D55208762)

[ghstack-poisoned]
Step 1 of release process: Create a release branch.

The branch is named with `release/MAJOR.MINOR`.

From executorch root, run `./scripts/release/cut-release-branch.sh` will cut a release branch off stable branch (`viable/strict`) by default. Use `GIT_BRANCH_TO_CUT_FROM=main ./scripts/release/cut-release-branch.sh` to cut off `main` branch.



Differential Revision: [D55208762](https://our.internmc.facebook.com/intern/diff/D55208762)

[ghstack-poisoned]
@guangy10
Copy link
Contributor Author

@guangy10 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@facebook-github-bot
Copy link
Contributor

@guangy10 merged this pull request in a13a953.

kedarnath03 pushed a commit to kedarnath03/executorch that referenced this pull request Jun 25, 2025
ghstack-source-id: 0c5c210
Pull Request resolved: pytorch/executorch#2567
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants