[
https://issues.apache.org/jira/browse/SOLR-14762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17290807#comment-17290807
]
Jan Høydahl commented on SOLR-14762:
------------------------------------
{quote}1. Make all changes to lucene-solr repo (features and fixes) that need
to be done for a 9.0 release - Get to about 90% done.
{quote}
Anshum, are you aware of any features or fixes on master that would need to
happen before the split?
Agree that it is better to start early. Solr relying on Lucene-SNAPSHOT should
work well. Any breaking changes committed to lucene main branch would then
break Solr, and we'd need to deal with it to proceed. This is a small price to
pay, as it will stabilize once we can depend on a released Lucene 9.
{quote}It may be easier for solr to convert the build code on branch 8x to
gradle
{quote}
Didn't quite get this. Are you suggesting to convert branch_8x to grade, so
Solr project can release its own 8.8.2 based on released Lucene 8.8.2?
> 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: [email protected]
For additional commands, e-mail: [email protected]