Hi John, the way I understand git-flow is that for frequent pre-releases the release branches are used, so master always points to the last stable release, currently this would be release/3.1.0 (created from the v3.1 tag).
As development on 3.1.1 begins a branch named release/3.1.1 is created from next, and as development on next comes along every 'stable' state (meaning all the tests run) of next is merged into release/3.1.1. Once the official 3.1.1 version is tagged and released the release/3.1.1 branch is merged into master and the release/3.1.1 branch becomes 'stale' and only important bugfixes are merged into it from that point on. How does this sound? Cheers, Alexis -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
