THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
See umbrella issue
The table below tries to imagine the future state of various project resources post-split, together with some related comments on how to get there.
| Current | Lucene | Solr TLP | Issues | Comment | |
|---|---|---|---|---|---|
| Main git repo | lucene-solr | lucene (new) | solr (new) | Fork old lucene-solr repo into two new (lucene and solr) | |
| Website repo | lucene-site | Keep lucene-site | solr-site |
| Post-work to do on both repos after split Update mailing list addresses, git repo info, download pages etc NB: lucene/solr needs a redirect and front page link for several months |
| Dev list | dev@lucene | dev@lucene | dev@solr | Post a message to dev@lucene about the new dev@solr mailing list | |
| User lists | java-user@lucene solr-user@lucene | java-user@lucene | user@solr | Post a message to solr-user@lucene about the new address. Auto-reply when posting to old list? | |
| Issues list | issues@lucene | issues@lucene | issues@solr | Setup JIRA and GitHub to send to correct list | |
| Builds list | builds@lucene | builds@lucene | builds@solr | Setup Jenkins to send to correct list | |
| Jenkins | Lucene / lucene* Lucene / solr* | Lucene / lucene* | Solr / solr* | Create new project in Jenkins and move over jobs from Lucene | |
| Release repo | lucene/java lucene/solr | lucene/java/ | solr/ (new) | Anything to setup with Infra? Old lucene/solr folder needs a new README to let people know of the new location README in new solr/ release repo needs to mention old and new archive | |
| Release procedures | dev-tools/scripts/ smoketest releaseWizard | Modify for project | Modify for project | Each project will adapt releaseWizard and other release scripts for their needs | |
| IRC, Slack | #solr-dev #lucene-dev ... | #lucene-dev | #solr-dev | (No change) | |
| JIRA | Already separate | ||||
| PGP KEYS file | lucene/KEYS | (same) | solr/KEYS | Prepare new KEYS file for the new Solr PMC | |