Skip to content

Development Process

Jump to bottom
andrei-radulescu-banu edited this page Nov 16, 2018 · 3 revisions
  • Check out private branch. In our example, the private branch is called `devel`.
  • Optionally set up Travis-CI and DockerHub builds on the private branch.
  • Do development, test build on all supported platforms
  • If using Travis-CI or DockerHub, check their build completion success
  • Create git Pull Request
  • Pull Request is automatically built by Travis-CI
  • One of code owners approves pull request.
  • If preserving the private branch, do `git checkout master; git pull; git checkout devel` to update its master branch after the pull request is checked in.

The bitdribble-doc repository

Changes to the bitdribble-doc repo follow the same process, preferably using the same branch name as the branch used in the bitdribble repo. The bitdribble-doc repo is, however, not built on Travis-CI, but on ReadTheDocs.com, which does not have support for building pull requests.

Clone this wiki locally