-
Notifications
You must be signed in to change notification settings - Fork 0
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
DM-46530: Write up and test backport procedure for Prompt Processing #202
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes look good to me, but not marking as approved
since there are still other reviewers.
|
||
.. code-block:: sh | ||
|
||
git checkout -b tickets/DM-XXXXX-X.Y tickets/DM-XXXXX |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here and later, did you mean:
git checkout -b tickets/DM-XXXXX-X.Y.Z tickets/DM-XXXXX
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, that was intentional -- it's the copy of tickets/DM-XXXXX
being merged into the X.Y
branch (by analogy to the -v23
suffix in the Science Pipelines policy).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, GitHub tracks each reviewer's approval/disapproval separately. 🙂
We will now have branches of the form release/X.Y.
f03e046
to
1afb7b6
Compare
This process is based on the Science Pipelines backport process at https://developer.lsst.io/work/backports.html, but streamlined to allow for rapid deployment.
This is analogous to building on merge to main, and makes it easier to do any final pre-release testing.
1afb7b6
to
2df2c7e
Compare
This PR documents how to backport bug fixes onto a release branch, and modifies the existing docs and workflows to account for the existence of release branches.