Kanban Workflow

PhantomJS is using the most recent feature of GitHub, project view, to manage issues and pull requests. Since this is a new feature and there is no established best practice yet, the following simple Kanban workflow is utilized.

The main project is called "Upcoming Release". This collects all work items covered in the next subsequent release. Once the release is imminent, the project will be renamed to associate it with the release version, e.g. "Release 2.5".

Every project has 4 (four) columns:

• Backlog column contains all issues accepted to be part of the release.
• In Progress column lists all open pull requests which address issues in Backlog.
• Merged column lists all closed pull requests previously listed in In Progress.
• Completed column contains all closed issues previously listed in Backlog.

A release is possible only if there is no more card in the Backlog and In Progress columns.

An illustrative walk-through of the process with the following collaborators: Adele, Beyoncé, and Drake.

1. Adele works on a defect scoped for the next release. She places the issue card in the Backlog column.
2. After a while, she has a fix and creates a corresponding pull requests. She places the card associated with the pull request in the In Progress column.
3. Beyoncé reviews Adele's pull request. She likes it and merges it. Beyoncé moves the card associated with the pull request to the Merged column.
4. Drake sees that Adele's pull request is merged. He pulls from the fresh branch, builds everything, verifies that the defect is resolved, and then closes the issue. Drake moves the issue card to the Completed column.