Looks good - thanks for putting this together! Cos
On Mon, Jul 06, 2015 at 06:11PM, Yakov Zhdanov wrote: > Igniters, > > As it has been discussed, we are applying an updated Git policy which > should be more flexible and transparent that we have now. > > Process is described here: > https://cwiki.apache.org/confluence/display/IGNITE/Sprint+Process > > I would also put points here (taken from the page above) > > - Master should become the development branch for the next release > (current sprint). > - Whenever current release (sprint) goes to QA, new branch should be > created from master. This way master can be used to develop functionality > of the next release. All release fixes get merged to release branch and > then to master. > - All individual ticket branches should be created off of the master > branch (or release branch if one exists - in this case changes get merged > to release branch and then to master branch). > - Git tag should be created for every release. > - All CI tests must pass before the merge of ticket branches to the > master (or release) branch. > > ignite-sprint-7 branch will be removed soon. > > Please let me know if anyone has questions. > > --Yakov
signature.asc
Description: Digital signature
