[
https://issues.apache.org/jira/browse/SOLR-16714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710122#comment-17710122
]
ASF subversion and git services commented on SOLR-16714:
--------------------------------------------------------
Commit 92c39fee856258684c7cad8939e9364e3e43bddc in solr's branch
refs/heads/branch_9x from Jan Høydahl
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=92c39fee856 ]
SOLR-16714 ReleaseWizard to add solrbot dependency upgrades to CHANGES (#1483)
> ReleaseWizard to add dependency upgrades to CHANGES
> ---------------------------------------------------
>
> Key: SOLR-16714
> URL: https://issues.apache.org/jira/browse/SOLR-16714
> Project: Solr
> Issue Type: Improvement
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> 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
