-
Notifications
You must be signed in to change notification settings - Fork 841
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
Added backport process documentation #3407
Added backport process documentation #3407
Conversation
Preview documentation changes for this PR: https://eui.elastic.co/pr_3407/ |
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.
Some small edits.
Suggestions/Questions:
- Should we require a standard release prior to the backport release if one or more commits being backported exist only on master? For instance,
23.2.0
is referenced but does not yet exist. - I like to do this this extra bit because npm's latest tag will be wrong: Point npm latest tag to the actual latest version -
npm dist-tags add @elastic/[email protected] latest --otp=
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.
Any reason we shouldn't just add this to the existing release page? That one is pretty short and this one is pretty closely related. At the very least we should probably cross link the two.
Co-authored-by: Greg Thompson <[email protected]>
Co-authored-by: Greg Thompson <[email protected]>
Co-authored-by: Greg Thompson <[email protected]>
Co-authored-by: Greg Thompson <[email protected]>
Co-authored-by: Greg Thompson <[email protected]>
Preview documentation changes for this PR: https://eui.elastic.co/pr_3407/ |
Co-authored-by: Greg Thompson <[email protected]>
Preview documentation changes for this PR: https://eui.elastic.co/pr_3407/ |
Documented each step during the
22.3.1
backport release, this is the result.