On Sun, Mar 01, 2009 at 11:06:53AM -0600, Andy Lester wrote: > So how about this for the workflow, Patrick: > > 1) Developer creates a branch to work on a feature or cleanup or > whatever > 2) Developer commits to dev/rakudo work branch however much she wants. > 3) Developer merges back to dev/rakudo master branch with a "squash" > option. > 4) Developer posts merge request to pmichaud (or whoever) > 5) Patrick does a cherry-pick with the --no-commit flag on rakudo/ > rakudo. > 6) Patrick tests out the patch, and commits when happy.
Works for me. > Sound reasonable? I'll go throw it on a "how to be a rakudo developer" > page. Please do. Pm
