About bit4j branches on git

There would be 2 main branches -

master develop master would be the branch holding the current in production code. develop would hold in development code.

Developers should branch out from develop. Make changes and then merge back to develop. When you think your code is ready to be used by the millions of bit4j users (we'll get to the million someday if we keep adding and pushing new code), you can merge develop to master.

So at any point, master would contain the latest stable build while develop would contain unstable, nightly and snapshot releases.

You can understand this model being followed better by reading the blog post that inspired this - http://nvie.com/posts/a-successful-git-branching-model/