stages.md

Define stages for changes to GraphQL specification

stages.md

@@ -0,0 +1,49 @@
+# Stages for changes to GraphQL specification
+
+## Stage -2: proposed change(optional)
+**Prerequisite**: Described problem/change should be specific to the content of GraphQL Specification and not be an implementation detail.
+
+**Purpose**: Filter out question, issues for other repos and engage community discussion.
+
+## Stage -1: PR requested(optional)
+**Prerequisite**: Issue should contain description of problem/usecase and proposed solution. 
+
+**Purpose**: Find member of community to be champion for this change.
+
+## Stage 0: Proposal
+**Prerequisite**: 
++ Initial version of spec changes
++ Filled checklist in PR description
+
+**Steps**: start review process on specification changes
+
+**Post-Acceptance Changes Expected**: Major
+
+## Stage 1: Draft
+**Prerequisite**: 
++ Finalized wording inside Specification document
++ Proposed spec changes don’t have any blind spots (not described edge-cases, missed changes to related part of spec, etc.)
+
+**Steps**: start working on “graphql-js” PR
+
+**Post-Acceptance Changes Expected**: Incremental
+
+## Stage 2: Candidate
+**Prerequisite**:
++ Prepared PR for graphql-js
++ Notify all members of GraphQL WG
++ Community consent on the proposed change. If it’s hard to achieve, add it to agenda of the next WG meeting.
++ No changes to the graphql and graphql-js PRs for at least last 7 days
+
+**Steps**: Merge graphql-js PR and release NPM package
+
+**Post-Acceptance Changes Expected**: only those deemed critical based on implementation experience
+
+## Stage 3: Merged
+**Prerequisite**:
++ At least one month since release of the graphql-js with proposed change
++ Community consent on proposed change. If it’s hard to achieve add to agenda of the next WG meeting.
+
+**Steps**: Merge PR into “master” branch
+
+**Post-Acceptance Changes Expected**: none