Thanks for the responses David, this helps me to improve the documentation for this process. I am proceeding with the dependency updates and so far it seems most of the time to be straight forward, with a question popping up every now and then. The only challenge so far has been the identification of related or blocking dependencies based on the changelogs provided by the libraries.
One question that popped up recently (Jan can probably answer that): If I create a PR for backporting a cherry-picked commit that was previously completed with Solrbot, will the CHANGES file be updated by the bot? If not, I believe that I should update that in the PR myself, right? For reference, here is such a PR: https://github.com/apache/solr/pull/2845. How would I proceed on this one? I would like to create for all backports pull requests, even if it is a simple cherry-pick where the tests succeed. Is this the recommended approach in this situation? And to not get blocked I would probably not wait for a reviewer if the tests pass. To clarify your question "I don't understand. Write permissions to where?", non-committers are probably not able to bring these PRs to completion, because they cannot create commits on them and, lets say, update the license file. At least that's what I experienced before on a PR from Eric. What I am also missing a bit is any deprecation warning from our tools. I haven't faced any yet and I'd like to update the code before merging if anything is deprecated. I am not sure if I just got lucky and there haven't been any deprecations for the dependencies I resolved, or if I haven't been warned and missed them. The topic about the Jetty blockers is probably worth its own thread, but to respond to Gus message: Jetty 10 may be a version we could work with, but it could mess up any ongoing work on updating Jetty. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
