You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@solr.apache.org by "Jan Høydahl (Jira)" <ji...@apache.org> on 2023/04/10 16:01:00 UTC

[jira] [Resolved] (SOLR-16714) ReleaseWizard to add dependency upgrades to CHANGES

     [ https://issues.apache.org/jira/browse/SOLR-16714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Høydahl resolved SOLR-16714.
--------------------------------
    Fix Version/s: 9.2.1
       Resolution: Fixed

> 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
>             Fix For: 9.2.1
>
>          Time Spent: 2h 20m
>  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-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org