Welcome to the Blaze_ Repo

This repository stores all of the issues that coorespond to larger features and interoperability on the different codebases (currently datashape, libdynd, and dynd). For bugs that relate to one component, please see those various components. It also contains special labels for `Huboard`_ to allow viewing all of the issues across multiple repositories.

These labels are repeated throughout the various wakari components. They're used in Huboards to help prioritize and organize the issues across many repositories.

0 - Inbox

This is where issues should start out. You don't have to explicitly set this label as it is implied.

1 - Backlog

Issues in this bucket are things we want to do, but are not on the horizon for implementation. Items labeled here need to be revisited every so often to ensure they are still valid.

2 - On Deck

These are issues that are slated for work in the next few weeks. Ideally, nothing should make it to the On Deck bucket without being assigned to someone.

3 - In Progress

Any task that is currently being worked on should move to this bucket. This gives the team visibility as to who is working on what. Nothing in this bucket should be unassigned.

4 - Ready for Review

Items here are include Pull Requests that are ready and meta issues that might comprise multiple, related issues.

5 - Done

This is the final resting place for all issues and pull requests that have been accepted and finished. This column shows both open and closed issues in GitHub. Inside Huboard, you can "Archive" cards that are in this column. This gives us one final step to take that shows an issue has not only been completed, but also signed off on. Think of this as the "Accept" stage from Pivotal Trackers.

Milestones are used throughout to group projects together. We use the format ``Blaze vX.X` for various releases. For example, we use Blaze v0.3 for the v0.3 release and Blaze v0.4 for the v0.4 release.