[
https://issues.apache.org/jira/browse/SOLR-14762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287801#comment-17287801
]
Jan Høydahl commented on SOLR-14762:
------------------------------------
Agree, for the main branches (yes, we should use this opportunity to switch to
"main"), it is not that hard.
Intuitively the {{branch_xx}} branches would still exist in both lucene and
solr repos because it is part of the history. But what if those branches were
R/O in solr (or moved to a history/branches/xx tag for less visibility), but
writable in lucene. Then we all agree that the 8.x.y line of bugfix/security
releases will happen in Lucene (possibly with an additional VOTE thread over in
dev@solr as well to??). That way we won't need to have three active repos in
parallel.
For the website I now have a solr-only branch with all lucene site stuff
removed, and it works well.
Idea: Perhaps we should keep the {{solr/}} folder in solr for some time after
the split, just so that pathches are easier to backport.
> 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]