[
https://issues.apache.org/jira/browse/SOLR-9110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295085#comment-15295085
]
Steve Rowe commented on SOLR-9110:
----------------------------------
bq. One question: is it really necessary to mention tests only commit at
CHANGES.txt ?
It isn't necessary, but it can be quite helpful, since CHANGES.txt is often
used as a way of understanding the project. For example, for the 6.0.1
release, I'm using CHANGES.txt to decide which issues to backport.
If we're more careful in the future with JIRA fix version setting, it's
possible that CHANGES.txt could be auto-generated from JIRA - I know some
projects do that, and it's been discussed in the past for Lucene/Solr.
> migrate SubQuery-, Join-, ChildFacet- tests to SolrCloudTestCase
> -----------------------------------------------------------------
>
> Key: SOLR-9110
> URL: https://issues.apache.org/jira/browse/SOLR-9110
> Project: Solr
> Issue Type: Sub-task
> Reporter: Mikhail Khludnev
> Assignee: Mikhail Khludnev
> Fix For: 6.1, master (7.0)
>
> Attachments: SOLR-9110.patch, SOLR-9110.patch, SOLR-9110.patch
>
>
> I want to migrate the following classes to SolrCloudTestCase
> * DistribJoinFromCollectionTest
> * TestSubQueryTransformerDistrib
> * BlockJoinFacetDistribTest
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
