<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Feature-Flags on dplabs — Software Engineering &amp; Technology Consultancy</title>
		<link>https://dplabs.tech/tags/feature-flags/</link>
		<description>Recent content in Feature-Flags on dplabs — Software Engineering &amp; Technology Consultancy</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Tue, 28 Jul 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://dplabs.tech/tags/feature-flags/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Trunk-Based Development vs GitFlow: What the Debate Is Actually About</title>
				<link>https://dplabs.tech/blog/trunk-based-vs-gitflow/</link>
				<pubDate>Tue, 28 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/trunk-based-vs-gitflow/</guid>
				<description>&lt;p&gt;The branching strategy debate is loudly opinionated in both directions. GitFlow advocates point to clean release management and isolated feature development. Trunk-based development advocates point to the evidence that short-lived branches correlate with higher engineering performance. Both sides are often talking past each other.&lt;/p&gt;&#xA;&lt;p&gt;The useful question is not &amp;ldquo;which is better&amp;rdquo; but &amp;ldquo;which fits our context&amp;rdquo; — and the context includes team size, release cadence, engineering practices, and the nature of the software being delivered.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
