search

agco / hapi-harvester

A JSONAPI 1.0 plugin for Hapi.
14 stars 3 forks source link

Consider using github flow instead of git-flow #48

Open dclucas opened 8 years ago

dclucas commented 8 years ago

I think hapi-harvester (as well as some of our other libs) lends itself for a more streamline branch flow. My suggestion would be to leverage github's: http://scottchacon.com/2011/08/31/github-flow.html

mavdi commented 8 years ago

Very interesting read. I do however wonder how they tackle the need for data migration with some issues when they so often deploy. That's the big mystery to me and would love to find out what a company such ad Github has in place for it.

I'm all for continuous delivery though, and we will be pushing to get there.

dclucas commented 8 years ago

Long delay before commenting on this one, sorry.

There's a number of strategies that can be combined to lessen the pain:

  1. Feature toggles are a must have for teams delivering that frequently, as a full feature may take multiple days (and merges) to get done

  2. 1 can be combined with blue/green db deployments. This means that dormant features which require db changes can be deployed whenever the team opts to. The DB change may just happen when the feature is toggled, or as an in-between step

vinnylinck commented 8 years ago

Github flow +1

ShurakaiSoft commented 8 years ago

I'm all for Github flow. Using it for PR #75.