Lightchain Core
#Environment IntelliJ (JDK1.8)
#Libraries
BitcoinJ
#Committing code Do not commit .idea files Always pull before pushing
#Deployment Flow Main branches
#Dev - develop branch
Use git branch to create a develop branch of the codebase rather than making edits directly to the master branch
#Staging
Once there's a realease candidate all all the code will be merged into a staging branch. Use git tag to tag a release candidate. If last minute code/commits or code changes need to be made, do so in the develop branch.
#Production - master branch
The last train stop Once testing has been performed in staging, and we have not been able to break the application, merge the code from staging into master.
#Supporting branches
These are the limited-life time branches, that will be removed
At the beginning each member will choose a feature to develop. The feature branch will exitst as long as the feature is in development. Once the feature has been completed, the code will be merged back into develop
A feature branch will exist in your local repo, not in origin
To start working on a new feature, branch off from the develop branch.
#Status
The team is currently working on a series of pre-releases on the way to version 1.0. See the roadmap for details.
#Staying in Touch
Contact the team and keep up to date using any of the following:
- The #Lightchain IRC channel on Freenode
- Our mailing list
- @decentralteam on Twitter
- [email protected]
- The DecentralBank thread on the Bitcointalk forum
- GitHub Issues