I think my message got buried among other messages, so starting a new thread.
With Solr established, I think we're ready to proceed with forking the
git repository from:
https://git-wip-us.apache.org/repos/asf/lucene-solr.git
to:
(Lucene)
https://git-wip-us.apache.org/repos/asf/lucene.git
(Solr)
https://git-wip-us.apache.org/repos/asf/solr.git
My plan is as follows:
1. DISABLE CI jobs and anything that pulls from current master. (Uwe,
would you do help me with this?)
2. Branch master to lucene/main and solr/main. Remove sibling
project's sources from each respective branch.
3. Create a wiping commit on master (leaving a note about Solr going
TLP and new repository locations).
4. Push these changes and branches to lucene-solr.git.
5. Push a git mirror of everything up to this point to Lucene and Solr
repositories.
6. Create and enable independent CI jobs for Lucene and Solr. (Again,
some help here would be needed).
7. If everything goes ok, pop a celebratory beer.
Just as a remainder - the development of branch_8x STAYS ON
lucene-solr. Cherry-picking of individual commits can still be done if
you have two remotes and know how to operate this (admittedly not a
newbie git workflow). Anyone not comfortable - use patches, they're
raw and work well on anything.
Mainline development proceeds in each project's repository independently.
Does Wednesday sound ok for this plan? Then it'd be a few work week
days to clean up the dust.
Dawid
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
With Solr established, I think we're ready to proceed with forking the
git repository from:
https://git-wip-us.apache.org/repos/asf/lucene-solr.git
to:
(Lucene)
https://git-wip-us.apache.org/repos/asf/lucene.git
(Solr)
https://git-wip-us.apache.org/repos/asf/solr.git
My plan is as follows:
1. DISABLE CI jobs and anything that pulls from current master. (Uwe,
would you do help me with this?)
2. Branch master to lucene/main and solr/main. Remove sibling
project's sources from each respective branch.
3. Create a wiping commit on master (leaving a note about Solr going
TLP and new repository locations).
4. Push these changes and branches to lucene-solr.git.
5. Push a git mirror of everything up to this point to Lucene and Solr
repositories.
6. Create and enable independent CI jobs for Lucene and Solr. (Again,
some help here would be needed).
7. If everything goes ok, pop a celebratory beer.
Just as a remainder - the development of branch_8x STAYS ON
lucene-solr. Cherry-picking of individual commits can still be done if
you have two remotes and know how to operate this (admittedly not a
newbie git workflow). Anyone not comfortable - use patches, they're
raw and work well on anything.
Mainline development proceeds in each project's repository independently.
Does Wednesday sound ok for this plan? Then it'd be a few work week
days to clean up the dust.
Dawid
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org