[ 
https://issues.apache.org/jira/browse/SOLR-17157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828159#comment-17828159
 ] 

ASF subversion and git services commented on SOLR-17157:
--------------------------------------------------------

Commit 57cb10121699752a3c4c629037d1c3a4181a8e93 in solr's branch 
refs/heads/jira/SOLR-17157 from Chris M. Hostetter
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=57cb1012169 ]

SOLR-17157: Upgrade to Lucene 9.10.0


> upgrade to Lucene 9.10.0
> ------------------------
>
>                 Key: SOLR-17157
>                 URL: https://issues.apache.org/jira/browse/SOLR-17157
>             Project: Solr
>          Issue Type: Task
>            Reporter: Christine Poerschke
>            Priority: Major
>              Labels: newdev
>
> Creating and leaving this Jira open for (new) devs to grab.
> optional steps before Lucene 9.10 is released:
>  * Q: what would be the benefit of these optional steps?
>  ** A: to potentially identify 9.9 to 9.10 regressions before 9.10 is 
> released.
>  * monitor the relevant {{dev@lucene}} threads e.g.
>  ** https://lists.apache.org/thread/w7smn82q5q5qsstqbpdxm5vnfw3y9ojh - discuss
>  ** https://lists.apache.org/thread/bwjr0vpo25dv8ydycbmo3130pgfktvf0 - 
> feature freeze
>  ** https://lists.apache.org/thread/stwn4gfrs1dmxjpwdf59plfpgtvsf9v6 - voting
>  * locally build {{main}} Solr against the latest {{branch_9_10}} Lucene as 
> per [https://github.com/apache/solr/blob/main/help/dependencies.txt#L111] 
> steps
>  ** open a draft pull request with changes
>  ** run the tests and report and/or investigate any failures
> upgrade steps once Lucene 9.10 is released:
>  * [https://lucene.apache.org/core/9_10_0/changes/Changes.html]
>  * [https://github.com/apache/solr/blob/main/dev-docs/lucene-upgrade.md]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to