[
https://issues.apache.org/jira/browse/SOLR-14759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17210437#comment-17210437
]
Jan Høydahl commented on SOLR-14759:
------------------------------------
This is encouraging. There's nothing wrong with doing more of the split before
the actual TLP split.
If we proceed with SOLR-14762 now, then we create a 'lucene' git repo with
lucene-standalone branch as master, and a 'solr' repo with solr-standalone as
master. Then all master/9.0 development would happen in these two repos, while
all 8.x development would happen in the old 'lucene-solr' repo. Back-porting to
8.x would be a pain, but perhaps most new features could be 9.x only, or
perhaps someone could cook up a script that converts a 'solr' repo patch into a
'lucene-solr' patch?
We could also use the repo split as an opportunity to rename master branch as
'main'.
> Separate the Lucene and Solr builds
> -----------------------------------
>
> Key: SOLR-14759
> URL: https://issues.apache.org/jira/browse/SOLR-14759
> Project: Solr
> Issue Type: Sub-task
> Components: Build
> Reporter: Jan Høydahl
> Assignee: Dawid Weiss
> Priority: Major
>
> While still in same git repo, separate the builds, so Lucene and Solr can be
> built independently.
> This is a preparation step which will make it easier to prune the new git
> repos post-split.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
