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

Michael McCandless commented on LUCENE-7446:
--------------------------------------------

+1 to revert my change :)  I wasn't sure what I was doing, but it managed to 
get me through that release.

> Fix back-compat version check in addVersion helper script
> ---------------------------------------------------------
>
>                 Key: LUCENE-7446
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7446
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Anshum Gupta
>            Assignee: Anshum Gupta
>            Priority: Minor
>         Attachments: LUCENE-7446.patch, LUCENE-7446.patch
>
>
> As part of the 5.5.3 post-release process, I was trying to bump up the number 
> to 5.5.4 on the release branch but ran into the following error:
> {code}
> Traceback (most recent call last):
>   File "dev-tools/scripts/addVersion.py", line 246, in <module>
>     main()
>   File "dev-tools/scripts/addVersion.py", line 221, in main
>     if current_version.is_back_compat_with(c.version):
>   File 
> "/Users/anshumgupta/workspace/lucene-solr/dev-tools/scripts/scriptutil.py", 
> line 75, in is_back_compat_with
>     raise Exception('Back compat check disallowed for newer version: %s < %s' 
> % (self, other))
> Exception: Back compat check disallowed for newer version: 5.5.3 < 5.5.4
> {code}
> I think the check is wrong and should be reversed. I'll post a patch that I 
> used to work around this but would be good to have more eyes on this before I 
> commit this.
> [~steve_rowe]: Can you take a look at the patch as I guess you added this 
> recently.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to