[
https://issues.apache.org/jira/browse/SOLR-14762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287760#comment-17287760
]
Dawid Weiss commented on SOLR-14762:
------------------------------------
I thought about it some more and perhaps we should just start early (even
before the git repo is set up!) by making two branches off the current "master"
branch – say main/lucene and main/solr. Initially these would be identical but
I'd just hack and remove the "other" project from each of these branches. We
can then actually remove the contents of master entirely – lucene/main and
solr/main would become the entry points for each corresponding project's
repository, once it's created.
The benefit of doing these two branches is that we could start right away. Once
the contents of "master" is removed nobody can file a reasonable PR against
it... they'd have to pick between lucene/main or solr/main. Also, we could
start removing and separating the build code on each corresponding branch
without waiting for the new git repos (we would just clone the tree at any
convenient moment).
What do you think?
> 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
