https://jimolloy.com/categories/release/ Recent content in Release on Ji Molloy https://jimolloy.com/assets/images/eevee-on-computer-circle.png https://jimolloy.com/assets/images/eevee-on-computer-circle.png Hugo -- 0.163.0 en-us Sun, 06 Apr 2025 16:16:34 +1200 https://jimolloy.com/posts/2025/modern-software-delivery/ Sun, 06 Apr 2025 16:16:34 +1200 https://jimolloy.com/posts/2025/modern-software-delivery/ <p><img alt="alt text" loading="lazy" src="https://jimolloy.com/assets/images/tbd-eevee-charizard.png"></p> <p>Software delivery has changed a lot over the years! What’s the difference between <strong>continuous delivery</strong> and <strong>continuous deployment</strong>? 🤔</p> <p>And is a feature <code>live</code> just because it’s deployed? 🤨</p> <p>Let’s look into this together with some modern DevOps 🚀</p> <hr> <h2 id="-trunk-based-development">🌳 Trunk-Based Development</h2> <p>Trunk-based development (TBD) is a software development strategy where everyone works from a single branch (trunk) — usually <code>main</code>. It’s fast, lean, and fits in modern delivery practices.</p> <h3 id="-how-it-works">🔧 How it works:</h3> <ul> <li>Developers commit to <code>main</code> (or short-lived branches that are merged quickly to the <code>main</code> branch)</li> <li>The <code>main</code> branch is always deployable</li> <li>Features are hidden behind flags until they’re ready to go live 🚀</li> </ul> <h3 id="-why-it-matters">💡 Why it matters:</h3> <p>Trunk-based development encourages:</p>