All - I have been thinking about how to go about introducing branches for POCs or features that are not quite ready for prime time.
Kevin and I have discussed it a bit offline and have a high level proposal for it. We can create feature branches that are named after jira that represent the feature being worked on. We would probably want to keep the number of branches to a minimum though. So, we could use something like the following criteria: 1. when a feature is being POC'd or is a longer term effort it may overlap with a branching for release therefore these should be in a feature branch 2. larger efforts that have a number of jira's associated with them should be in a branch that represents the umbrella jira for the feature instead of a branch per jira 3. features that are complete and ready for release can go directly into master Alternatively, we can also consider using local feature branches for every jira - this would make working on multiple things at the same time easier/cleaner - but will also necessarily involve more branch merges and the like. thoughts? --larry
