Radium Core integration/staging tree
Clone or download
Pull request Compare This branch is 52 commits ahead, 11 commits behind CoinBlack:master.
Latest commit 7b59571 Nov 30, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
contrib fix linearize Jul 16, 2018
doc Increment version number Jul 16, 2018
share Increment version number Jul 16, 2018
src Update seed ip's Dec 1, 2018
.gitattributes Build identification strings Apr 10, 2012
.gitignore Radium renaming Dec 9, 2017
COPYING Radium renaming Dec 9, 2017
INSTALL Radium renaming Dec 9, 2017
README directory re-organization (keeps the old build system) Apr 23, 2011
README.md Radium GUI Dec 10, 2017
compile-radium.sh windows compile script Jul 16, 2018
radium-qt.pro Increment version number Jul 16, 2018


Radium development tree

Radium 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 radium.

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'.