Best Practices for working with the Inline::CPP Github repo

It's all about branches and tags...

'master' will always hold the latest full CPAN release. 'dev' contains progress on the development branch, as well as "Developers Release" versions for CPAN.

Bleeding edge, experimental, and work that could possibly break existing smoke-test success belongs in topic branches. Name topic branches for the type of work being done.

Successful topic branches will usually be merged into dev. When dev stabilizes it will be merged into master. Usually it will be best to start new topics by branching off of dev, but in some cases branching off of master will be necessary, although I've never needed to do so. I try to keep 'dev' "Developer's Release Ready."

Currently there is a 'tests' branch in the repo as well. This branch is being used for a test suite rewrite. It's a longer-term project, and occasionally I merge dev into tests so that as I work on the test suite it is working with the most recent developers version of Inline::CPP.

All CPAN uploads (stable or developers) have git tags. Tags look like either "v0.34" (stable), or "v0.34_002" (dev).

If you want access to contributing to this repo please get in touch with me.