Development Workflow

Motivation

This document defines the simple workflow that helps the developers could easily contribute to Casperdash repositories. We encourage our teams/contributors to follow them to ensure our projects:

• be easy to understand the workflow and quickly adapt
• have a common sense of thinking
• be less meeting/discussion and more things to be done

Following our roadmap here

1. Create an issue

You can create the new issues here. There are two types of issues

• Feature: suggest an idea/feature for this project

• Bug: create a report to help us improve

2. Milestone

Every week, the developer team will have a meeting with the product owner and pick up the issues to work on them. We will release the new features, bug fixes, and improvements in each milestone.

3. Project

You can follow the issue status in our project. There are the following statuses:

• TODO: when the task is newly added or reopened
• In progress: when the developer starts doing the task
• In Review: when the developer creates the pull request (PR) and waiting for the reviewer to approve the PR
• RFT: once the PR is approved and automatically deploys to testnet env.
• Done: when product owner/tester close the ticket

4. Git-flow

To standardize the git branch naming, we follow the git-flow branching model (https://github.com/nvie/gitflow).

branch	description
master	Branch name for production releases
develop	Branch name for "next release" development
feature/*	Feature branches
release/*	Releases branches
hotfix/*	Hotfix branches

5.Contributing

We alway welcome for any contributions or feedbacks Workflow for bug fixes:

• Check open issues and pull requests to make sure no duplicated topic
• Fork the repository
• Do your changes on your fork
• You need to cover or update relevant test cases
• Create a pull request, add fill the PR template