Skip to content
Joe Rezendes edited this page Dec 18, 2018 · 8 revisions

Welcome to the Skedge wiki!

This wiki defines Skedge's organizational flow.

Skedge uses a continuous delivery system where we develop in short cycles, ensuring that the software can be reliably released at any time and, when releasing the software, doing so manually.

This continues delivery system helps us at building, testing, and releasing software with greater speed and frequency.

Branch system

We will have the following Branches:

Master

The master branch will be the live version on https://www.skedge.io/

FeatureName

Each individual feature should have it's own branch that will merge into Master.

You should do the following before QA/Review/Merging into master.

  • Pull the master branch into your feature branch and resolve any merge conflicts
  • Do a final check to make sure nothing is broken or out of the ordinary.

Project Board

The following are some definitions:

  • Backlog: These are issues anyone can take.
  • In progress: You are working on this issue.
  • Ready: This issue is ready for Review/QA/Merge.
  • Done: This issue is shipped to production.
Clone this wiki locally