forked from PBSA/peerplays
-
Notifications
You must be signed in to change notification settings - Fork 18
Release Management & Versioning
Bobinson K B edited this page Aug 27, 2019
·
2 revisions
This document will capture the release management strategy, versioning, main and public net details etc.
For now, the branching strategy is updated as per https://github.com/peerplays-network/peerplays/pull/82
- We will be using
develop
branch for the non hardfork development activities. - Each developer needs to start development on a private branch based on
develop
- If the feature assigned is, GRPH-35, the branch can be
feature/GRPH-35
- Using Gitflow as described below is welcome
- PRs should be raised for all non-hardfork related features via github
- Avoid fast-forward merging
A good reference for Gitflow: https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow
Before starting the work, do the following
git checkout develop
git checkout -b feature/GRPH-35
Once the feature development is, completed, send the PR to develop
git checkout develop
git merge feature/GRPH-54