roadmap.md

supu.io : docs : roadmap

< Return to index

This is the roadmap document for the supu.io project. It describes the remaining work to do.

It is a live document, it means that changes on this spec are and will be comming if it is necessary. Nothing is fixed or closed unless we excplicity say the contrary. So please put everything in doubt and keep the discussion alive ;)

This document follows an idea started by Ubuntu, which consists in planning a great but difficult bug 0 (our 1.0 version) to solve, so all minor versions & milestones should refer this one and solve an small task and part of it.

Versioning

For transparency into our release cycle and in striving to maintain backward compatibility, all project components are maintained under the Semantic Versioning guidelines. Sometimes we screw up, but we'll adhere to those rules whenever is possible.

We also follow the rule that one issue fixed should be a new minor release, so expect to have a lot of minor version numbers changes, this will be normal.

0.1 : Managing issue tracker

• Issue Tracker interface
• Github Issue Tracker: Get a list of issues by status
• Github Issue Tracker: Update issue status
• Github Issue Tracker: Get issue details by id
• API to get a issues list by status
• CLI to get a issues list by status
• API to get an issue details
• CLI to get an issue details
• API to update an issue status
• CLI to update an issue status
• Github Issue Tracker: Create new issue
• API: Create new issue
• CLI: Create new issue
• Issue tracker setup
• Vagrant box based on chef

0.2 : On the path to a configurable webhooked service.

Introducing github-issues microservice

• Basic microservice structure (github-issues-microservice)
• POST /move (github-issues-microservice)

Workflow to be injected from the api

• Allow workflow.move to accept workflow definition (core)
• Move workflow.states.all calculation to api
• Move workflow.states.available calculation to api
• Send workflow definition to workflow.move (api)

Workflow to define webhooks for each step.

• Webhook calls must be extracted from the workflow definition (core)
• API should define the configured webhooks foreach transition (api)

0.3 : User authentication

0.4 : Linking the source control

• Source Control interface
• Github Source Control: Add a comment to pull request
• Github Source Control: Create a pull request
• Github Source Control: Accept pull request
• Github Issue Tracker: Add a comment to an issue
• WebHooked API to support github payloads

0.5 : Accounts

• WEB: create an account
• WEB: Configure Github Issue tracker
• WEB: Configure Github Source Control

0.6 : Multiple issue trackers

• Jira Issue Tracker: Get a list of issues by status
• Jira Issue Tracker: Update issue status
• Jira Issue Tracker: Add a comment to an issue
• Jira Issue Tracker: Get issue details by id
• WebHooked API to support Jira payloads
• Trello Issue Tracker: Get a list of issues by status
• Trello Issue Tracker: Update issue status
• Trello Issue Tracker: Add a comment to an issue
• Trello Issue Tracker: Get issue details by id
• WebHooked API to support Trello payloads
• WEB: configure your issue tracker

0.7 : Multiple source controls

• Bitbucket Source Control: Add a comment to pull request
• Bitbucket Source Control: Create a pull request
• Bitbucket Source Control: Accept pull request
• WEB: select your source control system
• WebHooked API to support Bitbucket payloads

Backlog

• To be defined
• API Error control