Hi Dawid, > My plan is as follows: > > 1. DISABLE CI jobs and anything that pulls from current master. (Uwe, > would you do help me with this?)
Yes, I can do this. I have meetings on Wednesday, but I can already do this tomorrow evening. > 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). Yes. Basically, we can duplicate the jobs and run the same command, just with different Git checkout. This needs to be done on ASF Jenkins and Policeman Jenkins. To do this, the easiest is to create a small batch job (that I already used on the ASF Jenkins Move), that extracts the Jenkins Config file of Jobs from the server, patches them and resubmits them under different name. That's much easier than manually editing them. I only need to create an API key. The workflow is here, easily adaptable for this usecase: https://cwiki.apache.org/confluence/display/INFRA/Migrating+jobs+from+Jenkins+to+Cloudbees > 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: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
