[
https://issues.apache.org/jira/browse/SOLR-16714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703223#comment-17703223
]
Kevin Risden commented on SOLR-16714:
-------------------------------------
How about just compare versions.props across branches? That should have all the
dependency upgrades we care about? We wouldn't have the PR linked to it but
would be able to highlight dependency upgrades?
> ReleaseWizard to add dependency upgrades to CHANGES
> ---------------------------------------------------
>
> Key: SOLR-16714
> URL: https://issues.apache.org/jira/browse/SOLR-16714
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Jan Høydahl
> Priority: Major
>
> With the 9.2 release we added {{solrbot}} and we typically merge dependency
> upgrades without separate CHANGES entries. However, there is now always a
> section "Dependency Updates" in CHANGES, and we need a way to fill that.
> My thinking is that the Release Wizard could run a script which will either
> run {{git log}} and find the commits done by solrbot on the release branch
> since last release, OR query GitHub for all PRs with a certain label or
> author. Problem with the github approach is that we currently don't record
> "fixed version" for PRs.
> Once the list of dependency upgrades are found, all that remains is to format
> it in CHANGES format and insert the list under the correct sub-section in
> CHANGES.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
