My release process notes from using the release wizard: My macOS system python3 didn't have some dependencies/modules, so I had to install the requirements.txt. I'm very unfamiliar with python dev practices in this regard... I wound up creating a venv and thus I ran python via /Users/dsmiley/DevSearch/solr_9x/dev-tools/scripts/.venv/bin/python3. However, some release wizard commands like invoking `addDepsToChanges.py` didn't work OOTB because it didn't know about my venv. I'm not sure how the script or my approach should be updated.
Question: https://ci-builds.apache.org/job/Solr/job/Solr-Docker-Nightly-9.x/ description says Moved to github workflows: https://github.com/apache/solr/actions/workflows/docker-nightly.yml but that is only true for main, not 9x nor even 10x. The GH screen shows this, not to mention the workflow yml file isn't on branch_9x (I didn't check 10x). Note: I updated https://cwiki.apache.org/confluence/display/SOLR/JenkinsReleaseBuilds+-+Solr replacing the reference of solr-reference-guide-official to Solr-reference-guide-9.x The CI builds I created are working except for the smoketester: https://ci-builds.apache.org/job/Solr/job/Solr-Smoketest-9.11/3/console > RuntimeError: did not see "Release 9.11.0" in > file:///home/jenkins/jenkins-agent/workspace/Solr/Solr-Smoketest-9.11/solr/distribution/build/release/changes/Changes.html > > On Mon, Apr 27, 2026 at 12:27 PM David Smiley <[email protected]> wrote: > NOTICE: > > Branch branch_9_11 has been cut and versions updated to 9.12 on the stable > branch. > > Please observe the normal rules: > > * No new features may be committed to the branch. > * Documentation patches, build patches and serious bug fixes may be > committed to the branch. However, you should submit all patches you > want to commit to Jira first to give others the chance to review > and possibly vote against the patch. Keep in mind that it is our > main intention to keep the branch as stable as possible. > * All patches that are intended for the branch should first be committed > to the unstable branch, merged into the stable branch, and then into > the current release branch. > * Normal unstable and stable branch development may continue as usual. > However, if you plan to commit a big change to the unstable branch > while the branch feature freeze is in effect, think twice: can't the > addition wait a couple more days? Merges of bug fixes into the branch > may become more difficult. > * Only Jira issues with Fix version 9.11 and priority "Blocker" will delay > a release candidate build. > >
