Skip to content
No description, website, or topics provided.
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
build-aux/m4 init Dec 23, 2018
contrib init Dec 23, 2018
depends init Dec 23, 2018
doc init Dec 23, 2018
share init Dec 23, 2018
src init Dec 23, 2018
test init Dec 23, 2018
.gitattributes init Dec 23, 2018
.gitignore init Dec 23, 2018
.travis.yml init Dec 23, 2018
Makefile.am init Dec 23, 2018
README.md init Dec 23, 2018
autogen.sh init Dec 23, 2018
configure.ac init Dec 23, 2018
libqubnetconsensus.pc.in init Dec 23, 2018

README.md

Qubnetchain development tree

Qubnetchain is a PoS-based cryptocurrency.

Development process

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if they don't match the project's coding conventions (see coding.txt) or are controversial.

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are regularly created to indicate new stable release versions of Qubnetchain.

Feature branches are created when there are major new features being worked on by several people.

From time to time a pull request will become outdated. If this occurs, and the pull is no longer automatically mergeable; a comment on the pull will be used to issue a warning of closure. The pull will be closed 15 days after the warning if action is not taken by the author. Pull requests closed in this manner will have their corresponding issue labeled 'stagnant'.

Issues with no commits will be given a similar warning, and closed after 15 days from their last activity. Issues closed in this manner will be labeled 'stale'.

You can’t perform that action at this time.