-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Create 2.9 release notes and clear out changelog #8682
Conversation
Signed-off-by: Andrew Ross <andrross@amazon.com>
Thanks @andrross ! |
Signed-off-by: Andrew Ross <andrross@amazon.com>
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
Codecov Report
@@ Coverage Diff @@
## main #8682 +/- ##
=========================================
Coverage 70.87% 70.88%
+ Complexity 57201 57198 -3
=========================================
Files 4771 4771
Lines 270312 270312
Branches 39505 39505
=========================================
+ Hits 191590 191611 +21
- Misses 62619 62623 +4
+ Partials 16103 16078 -25 |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-8682-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 3254efd7decd0d9a97caa69982286b1b90198585
# Push it to GitHub
git push --set-upstream origin backport/backport-8682-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.x Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.9 2.9
# Navigate to the new working tree
pushd ../.worktrees/backport-2.9
# Create a new branch
git switch --create backport/backport-8682-to-2.9
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 3254efd7decd0d9a97caa69982286b1b90198585
# Push it to GitHub
git push --set-upstream origin backport/backport-8682-to-2.9
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.9 Then, create a pull request where the |
* Create 2.9 release notes and clear out changelog Signed-off-by: Andrew Ross <andrross@amazon.com> * Move changes from 3.0 that were backported Signed-off-by: Andrew Ross <andrross@amazon.com> --------- Signed-off-by: Andrew Ross <andrross@amazon.com> (cherry picked from commit 3254efd)
* Create 2.9 release notes and clear out changelog Signed-off-by: Andrew Ross <andrross@amazon.com> * Move changes from 3.0 that were backported Signed-off-by: Andrew Ross <andrross@amazon.com> --------- Signed-off-by: Andrew Ross <andrross@amazon.com> (cherry picked from commit 3254efd)
…8682) * Create 2.9 release notes and clear out changelog Signed-off-by: Andrew Ross <andrross@amazon.com> * Move changes from 3.0 that were backported Signed-off-by: Andrew Ross <andrross@amazon.com> --------- Signed-off-by: Andrew Ross <andrross@amazon.com> Signed-off-by: sahil buddharaju <sahilbud@amazon.com>
…8682) * Create 2.9 release notes and clear out changelog Signed-off-by: Andrew Ross <andrross@amazon.com> * Move changes from 3.0 that were backported Signed-off-by: Andrew Ross <andrross@amazon.com> --------- Signed-off-by: Andrew Ross <andrross@amazon.com>
…8682) * Create 2.9 release notes and clear out changelog Signed-off-by: Andrew Ross <andrross@amazon.com> * Move changes from 3.0 that were backported Signed-off-by: Andrew Ross <andrross@amazon.com> --------- Signed-off-by: Andrew Ross <andrross@amazon.com> Signed-off-by: Shivansh Arora <hishiv@amazon.com>
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.