Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

See umbrella issue issues 

Jira
serverASF JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keySOLR-14497
 
 and 
Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyLUCENE-9375

Table of Contents

Project resources pre/post split

...


CurrentLuceneSolr TLPIssuesComment
Main git repo

lucene-solr

lucene (new)solr (new)

Jira
serverASF JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keySOLR-14759
Jira
serverASF JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keySOLR-14761
Jira
serverASF JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keySOLR-14762

Decide on conditions for the split
Decide a date for code freeze
Fork old lucene-solr repo into two new (lucene and solr)
Add a commit to README.md in old repo about where to find the new repos
Make old repo read only.

Website CMS repolucene-siteKeep lucene-sitesolr-site

Jira
showSummaryfalse
serverASF JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keySOLR-14499

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keySOLR-15189

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keySOLR-15177

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyLUCENE-9797

Jira
serverASF JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keySOLR-15593
 

Post-work to do on both repos after split
Update mailing list addresses, git repo info, download pages etc
NB: lucene/solr needs a perm 301 redirect (forever in htaccess) and front page link for several months

Update htaccess to add redirects from solr to new solr. Also change internal Subversion mod_rewrite (see below)

Website HTML repohttps://svn.apache.org/repos/infra/
websites/production/lucene/content
Keep lucenehttps://svn.apache.org/repos/infra/
websites/production/solr/content

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keySOLR-15177
  

Jira
serverASF JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keySOLR-15593

Data (Javadocs, Refguide HTML) needs to be svn-mv'ed.
User mail listsjava-user@lucene
solr-user@lucene
java-user@luceneuser@solrusers@solr

Jira
serverASF JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keySOLR-14760

Post a message to solr-user@lucene about the new address.
Auto-reply when posting to old list?
Issues mail listissues@luceneissues@luceneissues@solr

Jira
serverASF JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keySOLR-14760

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keySOLR-15207

Setup JIRA and GitHub to send to correct list
Builds mail listbuilds@lucenebuilds@lucenebuilds@solr

Jira
serverASF JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keySOLR-14760

Setup Jenkins to send to correct list
JenkinsLucene / lucene*
Lucene / solr*
Lucene / lucene*Solr / solr*

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keySOLR-15172

Create a new Folder named "Solr" (will be done by Infra, PMC gets access). Move jobs via dragdrop/move.

Release repolucene/java
lucene/solr
lucene/java/solr/ (new)

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keySOLR-15190

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 proceduresdev-tools/scripts/
smoketest
releaseWizard
Modify for projectModify for project

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keySOLR-15173

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyLUCENE-9809

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 filelucene/KEYS(same)solr/KEYS
Prepare new KEYS file for the new Solr PMC
GitHub PRslucene-solr PRslucene PRssolr PRs

PRs will be frozen (ReadOnly) together with the lucene-solr GitHub project
We'll document commands necessary to take a lucene-solr PR (branch) and merge it into new repos

Anchor
resolution
resolution
Draft board resolution

If you are a Lucene committer and want to be part of the new Solr PMC, please add your name to the draft resolution below:

...

resolution

...

...

(This temporary section was removed 2021-02-18, after project establishment)