[
https://issues.apache.org/jira/browse/SOLR-17988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18131215#comment-18131215
]
Nick Shanin edited comment on SOLR-17988 at 10/26/26, 3:51 AM:
---------------------------------------------------------------
🤖 _AI text below_ 🤖 _(reviewed by Nick Shanin)_
Status check on this ticket: Solr 10.0.0 has been released, and the property
name changes are covered in the Solr 10 major changes and upgrade notes. If
specific property transitions are still missing from the docs, naming them here
would let someone pick that up; otherwise this looks complete with the release.
Update: Actually the above is wrong and I'm working on it.
Update2: I posted a PR but it will be stuck in draft status for a while. Feel
free to use my branch.
was (Author: JIRAUSER314749):
🤖 _AI text below_ 🤖 _(reviewed by Nick Shanin)_
Status check on this ticket: Solr 10.0.0 has been released, and the property
name changes are covered in the Solr 10 major changes and upgrade notes. If
specific property transitions are still missing from the docs, naming them here
would let someone pick that up; otherwise this looks complete with the release.
Update: Actually the above is wrong and I'm working on it.
> Ensure Solr 10 Release Conveys Changes Users Need To Be Aware Of For
> Properties!
> --------------------------------------------------------------------------------
>
> Key: SOLR-17988
> URL: https://issues.apache.org/jira/browse/SOLR-17988
> Project: Solr
> Issue Type: Sub-task
> Components: documentation
> Affects Versions: 10.0
> Reporter: Eric Pugh
> Assignee: Eric Pugh
> Priority: Blocker
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Let's make sure we are properly conveying all the various changes in the Solr
> property names, and what that means to all the places you set them.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
