...
- Attach a patch, pull request url or branch name (see instructions at Workflow)
- (OPTIONAL) create an Upsource review: Review With Upsource
- Add comment describing what has been implemented.
- Move ticket to
PATCH AVAILABLE
state. - If there is a community member who you think should do the review, optionally assign the ticket to that person.
...
- Once ticket has passed all the reviews and has no additional comments, a committer should apply the latest patch to the master branch.
- A comment should be added to the ticket stating that the patch has been applied to master.
- Move ticket to
CLOSED
state.
Review With Upsource
- Register on http://reviews.ignite.apache.org/
- Go to Branches view: http://reviews.ignite.apache.org/ignite/branches
- Click on your pull request ("PR XXXX")
- Click "Create branch review"
- Rename review to include JIRA key and description (example: "IGNITE-42 Support CacheLoader and CacheWriter")
- In JIRA, use More -> Link -> Web Link to link the review page
TODO
Git Process
Ignite development is split into 2 week sprints. However, duration may be longer or shorter. Preferably, each sprint should end with a public release. After development is finished, QA cycle starts, then release procedure follows.
...