<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tracking Project History on Amit Agarwal Linux Blog</title>
    <link>/tags/tracking-project-history/</link>
    <description>Recent content in Tracking Project History on Amit Agarwal Linux Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Mon, 18 Dec 2017 01:00:56 +0000</lastBuildDate>
    
	<atom:link href="/tags/tracking-project-history/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Trunk-based Development vs. Git Flow</title>
      <link>/2017/12/18/trunk-based-development-vs-git-flow/</link>
      <pubDate>Mon, 18 Dec 2017 01:00:56 +0000</pubDate>
      
      <guid>/2017/12/18/trunk-based-development-vs-git-flow/</guid>
      <description>&lt;p&gt;In order to develop quality software, we need to be able to track all changes and reverse them if necessary. Version control systems fill that role by tracking project history and helping to merge changes made by multiple people. They greatly speed up work and give us the ability to find bugs more easily.&lt;/p&gt;
&lt;p&gt;Moreover, working in distributed teams is possible mainly thanks to these tools. They enable several people to work on different parts of a project at the same time and later join their results into a single product. Let’s take a closer look at version control systems and explain how trunk-based development and Git flow came to being.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
