[
https://issues.apache.org/jira/browse/LUCENE-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14128763#comment-14128763
]
Michael McCandless commented on LUCENE-5863:
--------------------------------------------
I think adding this to smoke tester is ok? Smoke tester is run by jenkins
periodically so if a release somehow gets out w/o TestBackCompat being updated,
we'll know before the next release.
I like that the check is "end to end" (does not know about / make assumptions
about implementation details like version constants). It's also not that
heavy: loads the URL from apache.org, runs 2 BWC tests, and then checks that
the versions it saw are the same ...
I agree it's somewhat redundant with the one-time version check plus ongoing
check for each release, but I think having some redundancy here is actually
really important (who tests the test testers!).
But separately I agree we should also have tests to confirm there is a version
constant for every still-supported release.
> Generate backwards compatibility indexes for all 4.x releases
> -------------------------------------------------------------
>
> Key: LUCENE-5863
> URL: https://issues.apache.org/jira/browse/LUCENE-5863
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Attachments: testTheBWCTester.py
>
>
> Currently the versioning here is a total mess, and its inconsistent across
> bugfix releases.
> We should just generate back compat indexes for every release: regardless of
> whether the index format changed, even for bugfix releases. This ensures at
> least we try to test that the back compat is working.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
