In this case to create a 0.0.3 we would probably want to create a branch from the 0.0.2 tag (possibly called something like "release-0.0"). When the 0.1.0 release is "ready" (and I'll try to get the documentation updated before that), the proposed model would be to create a "release-0.1" branch, test until comfortable, and then release 0.1.0 from that branch. Then if 0.1.1 should become necessary, we continue working from the "release-0.1" branch, cherry picking from master as needed.
Brandon On Tue, Mar 17, 2015 at 9:30 AM Joe Witt <[email protected]> wrote: > Hello > > With 0.0.2 behind us now we can start preperations for the next > planned release which is 0.1.0. In it we can include the stuff Dan > Bress had planned and we can start folding in some of these things > which have been on branches. > > My git/git-flow foo isn't up to par to understand the right way that > we'd do an 0.0.3 if we had to. But seems easy enough given the tag > and the fact that master is the view right after the release. > > Thanks > Joe >
