Introducing WunderFlow

Git is almost considered as the current standard of a modern version control tool. There are also a few established workflows build around Git to make the development process more convenient with good version control practices. Most notable one of such workflows is Git-flow. In addition to Git-flow, there are also others that have strong concepts like feature per branch and pull/merge based workflows. Each of those concepts are no doubt usable in different situations, but there are cases where none of them just feel right.

We have had many such cases, where we have felt like we need something more from a workflow. This is true especially when our customer projects are already launched and there is lots of continuous development still going on. Soon, we are in a situation where we have a live site with active small development, possibly some bigger continuous development project and occasional hotfixes. On top of that, there is usually customer testing and acceptance practices involved in the process.  All of these combined makes it hard to keep track of everything and do new releases with confidence. We should always be able to know for sure that only the features tested and accepted by the customer would be included in the release. 

We decided to do something about the workflow. We went through most of the well known Git workflows, but in the end didn't find one that would fit our needs. So we ended up developing our own workflow, distilling all the good practices we liked and found useable in other workflows.

In this session I will first go through the basic workflow structure of WunderFlow. I will also discuss the reasoning behind our decisions and demonstrate the issues we have addressed with WunderFlow. Finally I will give some practical examples of the workflow in different common case situations.

More info at http://wunderflow.wunder.io