<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>branching on Nelis&#39; blog</title>
    <link>https://nelis.boucke.be/tags/branching/</link>
    <description>Recent content in branching on Nelis&#39; blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Sun, 15 Mar 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://nelis.boucke.be/tags/branching/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Trunk-based development</title>
      <link>https://nelis.boucke.be/post/trunk-based-development/</link>
      <pubDate>Sun, 15 Mar 2020 00:00:00 +0000</pubDate>
      
      <guid>https://nelis.boucke.be/post/trunk-based-development/</guid>
      <description>Trunk-based development When it comes to software delivery speed and quality, trunk-based development is the way to go.
It took me a while to realize this myself. I used feature branches with pull-request as the main way of working (writeup of an experience of using pull request), so well aware of the advantages and disadvantages. But switching to Trunk based development felt very counterintuitive to me. For sure, the build would be broken all the time, and the quality would be horrible, especially with a larger group of people?</description>
    </item>
    
    <item>
      <title>Why and how do we use pull requests</title>
      <link>https://nelis.boucke.be/post/why-and-how-do-we-use-pull-request/</link>
      <pubDate>Wed, 04 Oct 2017 00:00:00 +0000</pubDate>
      
      <guid>https://nelis.boucke.be/post/why-and-how-do-we-use-pull-request/</guid>
      <description>The goal of this post is to share why teams I worked with used pull requests and how this was practically organized. Please note that I&amp;rsquo;m strongly in favor of using trunk-based development over pull requests, and I collected references to get you started in another post. But I still share experience, knowing it’s not a perfect example, as it might provide inspiration on the advantages and disadvantages of such an approach.</description>
    </item>
    
  </channel>
</rss>
