I agree that for most dep updates a committ message with PR link is enough. Or perhpaps we could write a script that release-wizard could run that adds a new section to CHANGES with all the dep updates in this release?
Jan > 27. feb. 2023 kl. 13:08 skrev Ishan Chattopadhyaya > <[email protected]>: > > <commit message> (#XXXX) > > where XXXX is the PR number is good enough. IntelliJ IDE understands this > format and makes it a clickable link. > > On Mon, 27 Feb, 2023, 3:51 pm Jan Høydahl, <[email protected] > <mailto:[email protected]>> wrote: >> Hi >> >> Current status is that solrbot has opened 25 Pull Requests with dependency >> upgrades. There are probably more, but we told the bot to rate limit on 25. >> If anyone wants to help triage which of these to include in the 9.2 release, >> feel free to walk through the list and either approve, comment or push >> changes: >> >> >> Pull requests · apache/solr >> github.com >> <https://github.com/apache/solr/pulls/solrbot>Pull requests · apache/solr >> <https://github.com/apache/solr/pulls/solrbot> >> github.com <https://github.com/apache/solr/pulls/solrbot> >> >> We also have to decide how to handle CHANGES entries for bot updates. My >> thinking is that many minor/patch upgrades may not need a changes line, >> while issues that also require some work in Solr code may need one, and that >> can be added in the PR branch by the committer. >> >> Many of these won't need a JIRA issue either, so this could be a good time >> to start adding Github PR numbers to CHANGES.txt. I think we already support >> these formats: >> >> * GH#123: Update foo to 1.2.3 >> * GITHUB#123: Update foo to 1.2.3 >> * GH-123: Update foo to 1.2.3 >> * GITHUB-123: Update foo to 1.2.3 >> * github pull request 123: Update foo to 1.2.3 >> >> Any thoughts? >> >> Jan >> >>> 24. feb. 2023 kl. 10:34 skrev Jan Høydahl <[email protected] >>> <mailto:[email protected]>>: >>> >>> Hi all devs, >>> >>> We are testing dependabot-style PRs for dependency updates. >>> So be prepared to see new PRs opened by a bot user called "solrbot" (which >>> I'm maintaining). >>> Initially there will be quite a few of these, and after that a once-a-week >>> batch of new PRs. >>> >>> See >>> https://github.com/apache/solr/blob/main/dev-docs/dependency-upgrades.adoc >>> for some dev-docs about the feature. >>> >>> Hoping this will be a positive contribution to the project's dependency >>> health. >>> Please bear over with us as we tune the schedule and sensitivity of the >>> bot, so it's not too noisy :) >>> >>> Jan >> > <solr.png> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected]
