Versions Compared

Key

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

...

  1. If you don't have the necessary permissions for creating a new page, please ask on the development mailing list.
  2. Create a page which is a child of this one. Take the next available SIP number and give your proposal a descriptive heading. e.g. "SIP 42: Solr API v3".
  3. Fill in the sections as described above
  4. Start a [DISCUSS] thread on the mailing list. Please ensure that the subject of the thread is of the format [DISCUSS] SIP-{your SIP number} {your SIP heading}. Discussion can also happen on the WIKI page for the SIP by using Confluence inline commenting system (Mark the words you want to comment and clik the comment icon that pops up).
  5. When feedback iteration trails off on the DISCUSS thread, move to either adopt the proposal.  To do this you can either:
    1. rely on lazy consensus - announce your intention to proceed with the SIP as written unless there are any further objections, then wait 3 business days for readers to object or request an explicit VOTE instead.
    2. Alternatively, you can jump right to calling a formal VOTE.  Create a VOTE thread that points readers to your proposal and ask for votes. The criteria for acceptance is consensus (3 binding +1 votes and no binding vetoes).  Once a VOTE thread is created, add a link to the table below so the outcome can be tracked clearly.
  6. If the proposal was accepted, move the SIP from the "Under Discussion" table to the "Adopted" table below.  If the proposal failed to pass, move the SIP to the "Discarded" table.
  7. Implement the SIP.
  8. When implementation is complete, move the SIP to the "Implemented" table below.

SIP round-up

Next SIP Next SIP Number: 1516

Use this number as the identifier for your SIP and increment this value.

...

SIPStateLink to JIRALink to dev@ Discussion Thread
SIP-1: Streamline Config/Schema APIsDiscuss

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


SIP-2 Support safe index transformations without reindexingDiscuss

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


SIP-3 Solr-specific log and thread indexing and UIDiscuss

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


SIP-4 Resource management frameworkDiscuss

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


SIP-5 Coordination Module + Apache CuratorDiscuss

SIP-6 Solr should own the bootstrap processDiscuss

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

Mail thread
SIP-7 Updated Solr Admin UIDiscuss

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

Mail thread
SIP-9 Advanced Query ParserDiscuss

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

Mail thread
SIP-11 Uniform cluster-level configuration APIDiscuss

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

Slack thread
SIP-13: Cross Data Center ReplicationDiscuss
Mail thread
SIP-14 Embedded ZookeeperDiscuss

SIP-15 Node rolesDiscuss

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



Adopted/Accepted but unreleased SIPs

...