[
https://issues.apache.org/jira/browse/SOLR-14762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17290225#comment-17290225
]
Dawid Weiss commented on SOLR-14762:
------------------------------------
I think it should be sooner than later. Solr can depend on lucene snapshots
(published on apache nexus). Keeping things together won't make the problem of
splitting builds/ infrastructure easier, it just delays the work needed. Let's
do it early and then both projects can choose to go forward however they want.
It may be easier for solr to convert the build code on branch 8x to gradle, for
example, treating Lucene as a pure build dependency.
> Fork the git repo into two new 'lucene' and 'solr'
> --------------------------------------------------
>
> Key: SOLR-14762
> URL: https://issues.apache.org/jira/browse/SOLR-14762
> Project: Solr
> Issue Type: Sub-task
> Reporter: Jan Høydahl
> Priority: Major
>
> Existing git repo (and GitHub project) will be frozen and two new repos used
> # Announce on all lists a date when the lucene-solr git repo will be frozen
> This date should be e.g. 14 days in the future to allow in-flight commits and
> PRs to be pushed
> # At the freeze date, make a last commit adding a big announcement to
> README.md about the location of the new repositories, then make both asf-git
> and github R/O
> # Clone 'lucene-solr' into new 'lucene' and 'solr' git repos
> Then continue with separate LUCENE and SOLR jiras to prepare the new repos,
> builds etc
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
