ppkarwasz commented on PR #3852: URL: https://github.com/apache/logging-log4j2/pull/3852#issuecomment-3149979755
Here's an improved and concise version of your PR comment: --- I’m wondering about the best approach to maintain synchronization between `2.x` (stable) and `main` (next major release). @vy, what do you think about **consistently** performing one of these actions **before** merging any PR to `2.x`: * Create a corresponding PR to cherry-pick changes into `main`. * Open an issue explicitly tracking the synchronization of each PR merged into `2.x`. * Clearly document in the PR comment why a change does not need to be ported to `main`. This approach would ensure we avoid accumulating backlog and helps us verify merges effectively. In this specific case, the change does **not** need porting because the modified method was already **removed** from `main` (verified). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
