Jonathan… Thanks for the wiki page. This is great. Before reading it, I was a bit confused on how feature branches work.
Based on the content of your wiki page, it seems like a feature branch should be related to an Epic and then all commits to that branch should be related to child JIRAs of that Epic. Would this be a good approach to take, or would the additional Epic create too much unnecessary overhead? Rob On 9/26/16, 9:11 AM, "Jonathan Hurley" <[email protected]> wrote: Hi Apache developers, I put together a simple wiki page outlining the strategy for using feature branches which I think will help us keep our trunk branch stable as we move forward with new development: https://cwiki.apache.org/confluence/display/AMBARI/Git+Feature+Branches Please have a look and feel free to provide feedback or edit it. The goal was to keep it simple and introduce committers to the feature branch workflow. We should all adopt this practice for both new features as well as non-feature changes which could potentially destabilize trunk.
