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

Mark Miller commented on LUCENE-6938:
-------------------------------------

We don't need to vote yet - that only happens when consensus fails or someone 
wants to force something. We can warn the dev list again to make sure everyone 
is caught up, but no need to force a vote unless someone comes out against. 
There is a very visible discussion and a few JIRA issues that have been in 
progress for a long time now. Once we are ready to go, we can sum things up in 
a new dev thread.

I think in terms of what needs to be covered here, Uwe has detailed it pretty 
well. We want all the targets to work really - or to understand why any target 
does not work. We can wait for Uwe to create a new git validator though - all 
targets still work without that. 'svn' does not really have a very deep imprint 
in our build targets.

I think the main thing left to do in this issue is put the git hash in 
efficiently.

Some other things people are concerned about can get further JIRA issues, but I 
imagine a lot of that (such as python scripts) can be updated as used / needed 
by those that use them.

> Convert build to work with Git rather than SVN.
> -----------------------------------------------
>
>                 Key: LUCENE-6938
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6938
>             Project: Lucene - Core
>          Issue Type: Task
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>         Attachments: LUCENE-6938.patch
>
>
> We assume an SVN checkout in parts of our build and will need to move to 
> assuming a Git checkout.
> Patches against https://github.com/dweiss/lucene-solr-svn2git from 
> LUCENE-6933.



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

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

Reply via email to