{"id":27629,"date":"2017-05-28T11:35:51","date_gmt":"2017-05-28T09:35:51","guid":{"rendered":"https:\/\/mamchenkov.net\/wordpress\/?p=27629"},"modified":"2017-05-28T11:35:51","modified_gmt":"2017-05-28T09:35:51","slug":"gitflow-considered-harmful-and-how-we-do-it","status":"publish","type":"post","link":"https:\/\/mamchenkov.net\/wordpress\/2017\/05\/28\/gitflow-considered-harmful-and-how-we-do-it\/","title":{"rendered":"GitFlow considered harmful, and how we do it"},"content":{"rendered":"\n

I came across this rather strongly opinionated blog post –\u00a0GitFlow considered harmful<\/a>, and I have to say that I mostly agree with it.<\/p>\n

In our company<\/a>, we use a similar approach to the Anti-gitflow, but with even more simplicity. \u00a0This is one particular thing I like so much about git is that each person, team, or company can pick the workflow that suits them best.<\/p>\n

Just to give you a little bit of context, we have a rather small development team (under 10 people), but we do a large number of projects. \u00a0All our projects are web-based, varying from small and simple websites (static HTML), through more complex WordPress sites (multilingual, e-commerce, etc), to business applications like CRMs. \u00a0Each project is done by several developers at a time and can later on be passed on to other developers, often much later (another iteration after several month). \u00a0Each developer is working on a number of projects at a time. \u00a0And we do very fast-paced development, often deploying multiple versions per day. \u00a0Given the nature of the projects and the development pace, we don’t ever really rollback. \u00a0Rollback is just another step (version) forward. \u00a0And we don’t have long and complex roadmaps in terms of which features will be released in which version. \u00a0It’s more of a constant review of what’s pending, what needs which resources, and what we can do right now. \u00a0(It’s far from ideal project management, but it somehow works for us. \u00a0If you think you can do better, send me your CV or LinkedIn profile, and we’ll talk.)<\/p>\n

In our case, we do the following:<\/p>\n