<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Git-Flow on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/git-flow/</link><description>Recent content in Git-Flow on Karpoke - Just Another Blog</description><generator>Hugo -- 0.167.0</generator><language>es</language><lastBuildDate>Sun, 16 Dec 2012 14:46:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/git-flow/index.xml" rel="self" type="application/rss+xml"/><item><title>A successful Git branching model</title><link>http://karpoke.ignaciocano.com/2012/12/16/a-successful-git-branching-model/</link><pubDate>Sun, 16 Dec 2012 14:46:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2012/12/16/a-successful-git-branching-model/</guid><description>&lt;blockquote&gt;
&lt;p&gt;In this post I present the development model that I’ve introduced for
all of my projects (both at work and private) about a year ago, and
which has turned out to be very successful. I’ve been meaning to write
about it for a while now, but I’ve never really found the time to do
so thoroughly, until now. I won’t talk about any of the projects’
details, merely about the branching strategy and release management.&lt;/p&gt;
&lt;/blockquote&gt;</description></item></channel></rss>