Joomla development process

<section data-background="images/25-joomla-development/verbeteringen-in-joomla.jpg" data-state="frontpage">
<div class="atitle2" style="padding:10px;background-color: rgba(0, 0, 0, 0.7);">how it works...<br>
    <div class="atitle" style="font-size:200% !important"><span class="db8orange">Joomla</span><br>development process</div>
        <br><br><br><br>
        <span class="apage1">by Peter Martin / <a href="https://db8.nl" target="_blank">db8.nl</a></span>
        <br>
        <span class="apage1">slides: <a href="https://slides.db8.nl" target="_blank">https://slides.db8.nl</a></span>
        <style>.atitle{text-shadow: 2px 2px 2px #000;}
        .atitle2{text-shadow: 2px 2px 2px #000;}
        </style>
        <div style="margin: 0 auto;">
        <a href="https://db8.nl" title="Joomla Specialist db8 Nijmegen" target="_blank">
            <img height="50" style="border:0;background:transparent;margin-right:20px;
            box-shadow: 0 0 0 rgba(0, 0, 0, 0.15);" src="images/db8-logo.svg" alt="db8">
        </a>
    </div>
</div>

---

<div class="title">Core <span class="db8orange">Joomla Development</span><br>
    <ul style="font-size: 70%">
        <li>Joomla versions</li>
        <li>Bugs / Feature requests</li>
        <li>Pull Requests</li>
        <li>git workflow</li>
        <li>Questions</li>
    </ul>
</div>

---

<div class="title">Joomla <span class="db8orange">Versions</span></div>

----

<h3>📖 <span class="db8orange">Semantic Versioning</span> (SemVer)</h3>

<p>Version number format: <span class="db8orange">x.y.z</span></strong></p>

<table border="1" cellpadding="6" cellspacing="0">
  <thead>
    <tr>
      <th>Part</th>
      <th>Meaning</th>
      <th>When It Changes</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>x</strong> – <span class="db8orange">MAJOR</span></td>
      <td>Breaking changes</td>
      <td>incompatible API changes</td>
    </tr>
    <tr>
      <td><strong>y</strong> – <span class="db8orange">MINOR</span></td>
      <td>New features,<br>backwards-compatible</td>
      <td>functionality added<br>without breaking existing features</td>
    </tr>
    <tr>
      <td><strong>z</strong> – <span class="db8orange">PATCH</span></td>
      <td>Bug fixes,<br>backwards-compatible</td>
      <td>bugs are fixed<br>without changing the API</td>
    </tr>
  </tbody>
</table>

----

<h3>🚦 <span class="db8orange">Release Phases</span><br>for Major Releases</h3>

<table border="1" cellpadding="6" cellspacing="0">
  <thead>
    <tr>
      <th>Phase</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Alpha</td>
      <td>New features are added and tested</td>
    </tr>
    <tr>
      <td>Beta</td>
      <td>Feature freeze, <span class="db8orange">no new features</span>,<br>only bugfixes</td>
    </tr>
    <tr>
      <td>Release Candidate (RC)</td>
      <td>Language freeze, final testing,<br><span class="db8orange">no changes to language strings</span></td>
    </tr>
    <tr>
      <td>Stable</td>
      <td>Only bug fixes are applied,<br>production-ready</td>
    </tr>
  </tbody>
</table>

----

<h3>📋 <span class="db8orange">Joomla Versions</span></h3>

<table border="1" cellpadding="6" cellspacing="0">
  <tbody>
    <tr>
      <td><strong>Date</strong></td>
      <td>April 2025</td>
    </tr>
    <tr>
      <td><strong>Current Version</strong></td>
      <td>Joomla 5.3.0</td>
    </tr>
    <tr>
      <td><strong>Roadmap</strong></td>
      <td><a href="https://developer.joomla.org/roadmap.html" target="_blank">https://developer.joomla.org/roadmap.html</a></td>
    </tr>
  </tbody>
</table>

----

<h3>✅ <span class="db8orange">Current</span> Stable Release</h3>

<table border="1" cellpadding="6" cellspacing="0">
  <thead>
    <tr>
      <th>Branch</th>
      <th>Link</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>5.3-dev</td>
      <td><a href="https://github.com/joomla/joomla-cms/tree/5.3-dev" target="_blank">github.com/joomla/joomla-cms/tree/5.3-dev</a></td>
    </tr>
    <tr>
      <td>5.4-dev</td>
      <td><a href="https://github.com/joomla/joomla-cms/tree/5.4-dev" target="_blank">github.com/joomla/joomla-cms/tree/5.4-dev</a></td>
    </tr>
  </tbody>
</table>
<br>
<table border="1" cellpadding="6" cellspacing="0">
  <tbody>
    <tr><td>Current Release</td><td>5.3.0</td></tr>
    <tr><td>Upcoming Release</td><td>5.3.1</td></tr>
    <tr><td>Release Date of Series</td><td>17 October 2023</td></tr>
    <tr><td>End of Regular Bugfix Support (5.x)</td><td>13 October 2026</td></tr>
    <tr><td>End of Security Fix Only Support (5.x)</td><td>12 October 2027</td></tr>
  </tbody>
</table>

----

<h3>🔧 <span class="db8orange">Maintenance</span> Release</h3>

<table border="1" cellpadding="6" cellspacing="0">
  <thead>
    <tr>
      <th>Branch</th>
      <th>Link</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>4.4-dev</td>
      <td><a href="https://github.com/joomla/joomla-cms/tree/4.4-dev">github.com/joomla/joomla-cms/tree/4.4-dev</a></td>
    </tr>
  </tbody>
</table>

<br>
<table border="1" cellpadding="6" cellspacing="0">
  <tbody>
    <tr><td>Current Release</td><td>4.4.13</td></tr>
    <tr><td>Release Date of Series</td><td>17 August 2021</td></tr>
    <tr><td>End of Regular Bugfix Support (4.x)</td><td>15 October 2024</td></tr>
    <tr><td>End of Security Fix Only Support (4.x)</td><td>14 October 2025</td></tr>
  </tbody>
</table>

----

<h3>🚀 <span class="db8orange">Future</span> Release</h3>

<table border="1" cellpadding="6" cellspacing="0">
  <thead>
    <tr>
      <th>Branch</th>
      <th>Link</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>6.0-dev</td>
      <td><a href="https://github.com/joomla/joomla-cms/tree/6.0-dev">github.com/joomla/joomla-cms/tree/6.0-dev</a></td>
    </tr>
  </tbody>
</table>

<br>
<table border="1" cellpadding="6" cellspacing="0">
  <tbody>
    <tr><td>Upcoming Release</td><td>6.0.0</td></tr>
    <tr><td>Release Date of Series</td><td>14 October 2025</td></tr>
    <tr><td>End of Regular Bugfix Support (6.x)</td><td>17 October 2028</td></tr>
    <tr><td>End of Security Fix Only Support (6.x)</td><td>16 October 2029</td></tr>
  </tbody>
</table>

---

<div class="title"><span class="db8orange">Bugs</span> / <span class="db8orange">Feature requests</span></div>

----

<h2>🐞 <span class="db8orange">Bugs</span>, Hidden Features, and Other Shenanigans</h2>

<li>Bug in current Joomla website?
    <ul>
      <li class="fragment"><span class="db8orange">Test with</span> Joomla's <span class="db8orange">Cassiopeia</span> template.
        <ul>
          <li class="fragment">Solved? Issue with template override</li>
        </ul>
      <br></li>
      <li class="fragment"><span class="db8orange">Test in clean current stable version</span>.
        <ul>
          <li class="fragment">Not solved? <span class="db8orange">Search</span> 
            <a href="https://issues.joomla.org/" target="_blank">issues.joomla.org</a> 
            or 
            <a href="https://github.com/joomla/joomla-cms/issues" target="_blank">github.com/joomla/joomla-cms/issues</a>.
          </li>
          <li class="fragment">Not yet reported? <span class="db8orange">Please report with instructions</span> on how to reproduce.</li>
        </ul>
      </li>
    </ul>
  </li>
</ul>

----

<h2>✨ <span class="db8orange">Feature requests</span>, Wishes, and Smart Ideas 1/2</h2>
<ul style="font-size: 80%">

<li><strong>Benefit many users?</strong><br> 
  Does it solve a  <span class="db8orange">common need</span> or just a niche issue <span class="db8orange">?</span>
<br><br></li>

<li class="fragment"><strong>Extension already available?</strong><br> 
  Could  <span class="db8orange">existing extensions</span> solve this?
<br><br></li>

<li class="fragment"><strong>Align with Joomla's vision?</strong><br> 
   <span class="db8orange">Flexibility, security, accessibility</span> in mind?
<br><br></li>

<li class="fragment"><strong>Increase complexity?</strong><br> 
  Keep Joomla clean and  <span class="db8orange">easy to maintain</span>
<br><br></li>

</ul>

----

<h2>✨ <span class="db8orange">Feature requests</span>, Wishes, and Smart Ideas 2/2</h2>
<ul style="font-size: 80%">

<li><strong>Technically feasible?</strong><br> 
   <span class="db8orange">Avoid</span> ideas that would require  <span class="db8orange">massive changes</span>
<br><br></li>

<li class="fragment"><strong>Maintainable long-term?</strong><br> 
  Consider  <span class="db8orange">future updates</span> and support needs.
<br><br></li>

<li class="fragment"><strong>Possible to split into phases?</strong><br> 
   <span class="db8orange">Smaller steps</span> are more likely to succeed.
<br><br></li>

<li class="fragment"> <span class="db8orange">Suggest it</span> at: <a href="https://github.com/joomla/joomla-cms/issues" target="_blank">github.com/joomla/joomla-cms/issues</a></li>
</ul>

---

<div class="title"><span class="db8orange">Pull Requests</span> (PR)</div>

----

<h3>🔀 Pull Requests in Joomla 1/3</h3>

<li><strong>Understand what a Pull Request is</strong><br>
    A <span class="db8orange">Pull Request</span> is a request to have your code reviewed and merged ("pulled") into the Joomla core.
  <br><br></li>

<li><strong>Make a fork, create a branch, make changes</strong><br>
    <span class="db8orange">Fork the Joomla</span> CMS repository, create a properly named branch, make your changes, and submit them as a Pull Request (PR).
  <br><br></li>

<li><strong>Follow the coding standards</strong><br>
    Ensure your code matches the <a href="https://manual.joomla.org/coding-standards/" target="_blank">Joomla Coding Standards</a>.
  </li>

</ul>

----
<h3>🔀 Pull Requests in Joomla 2/3</h3>

<li><strong>Always base your PR on the <span class="db8orange">correct branch</span></strong><br>
    For bug fixes: branch from <code>staging</code>.  
    For new features: branch from <code>5.4-dev</code> (or the appropriate next minor).
  <br><br></li>

<li><strong>One pull request = one logical change</strong><br>
    <span class="db8orange">Keep PRs focused</span>. Avoid bundling unrelated fixes or features together.
  <br><br></li>

<li><strong>Write a clear title and description</strong><br>
    <span class="db8orange">Explain</span> what the PR does, why it’s needed, and how to test it.
  <br><br></li>

<li><strong>Check before submitting</strong><br>
    Run tests, check coding style, and manually <span class="db8orange">test your changes</span>.
  <br><br></li>
</ul>

----

<h3>🔀 Pull Requests in Joomla 3/3</h3>

<li><strong>Link related issues</strong><br>
    Mention <span class="db8orange">related GitHub</span> IDs, e.g., <code>Fixes #12345</code>.
  <br><br></li>

<li><strong>Be ready for review feedback</strong><br>
    Reviews are normal! <span class="db8orange">Update your PR</span> if changes are requested.
  <br><br></li>

<li><strong>Keep your branch updated</strong><br>
    Regularly pull changes from the base branch to <span class="db8orange">avoid conflicts</span>.
  <br><br></li>
</ul>

----

- Submitted PR 
- <span class="db8orange">Automatic tests</span>:
  - continuous-integration/appveyor/pr
  - continuous-integration/drone/pr
- Needs <span class="db8orange">2 successful human tests</span>
- Ready To Commit (<span class="db8orange">RTC</span>)
- Release Managers might merge it

---

<div class="title">git <span class="db8orange">workflow</span></div>

----

### Git Workflow

<table border="1" cellpadding="6" cellspacing="0">
  <thead>
    <tr>
      <th>Branch(es)</th>
      <th>Purpose</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><span class="db8orange">main</span><br>(or master)</td>
      <td>Same code as <span class="db8orange">production</span></td>
    </tr>
    <tr>
      <td><span class="db8orange">hotfix</span> branches</td>
      <td>Created from <strong>main</strong> to quickly <span class="db8orange">fix</span> critical <span class="db8orange">bugs in production</span></td>
    </tr>
    <tr>
      <td><span class="db8orange">develop</span></td>
      <td>The <span class="db8orange">next version</span> with features and improvements</td>
    </tr>
    <tr>
      <td><span class="db8orange">feature</span> branches</td>
      <td>Created from <strong>develop</strong> to add <span class="db8orange">new features</span></td>
    </tr>
    <tr>
      <td><span class="db8orange">release</span> branches</td>
      <td>Created from <strong>develop</strong> to <span class="db8orange">prepare new production release</span>, merged back into <strong>main</strong> and <strong>develop</strong></td>
    </tr>
  </tbody>
</table>

----

### Git Workflow

<span style="font-size:70%">
<a href="https://nvie.com/posts/a-successful-git-branching-model/" target="_blank">
A successful Git branching model</a> - Vincent Driessen, 5 January 2010
</span>

---

<div class="title"><span class="db8orange">Questions?</span></div>

----

## Photo Credits

<ul style="font-size:50%">
<li>https://unsplash.com/photos/white-printer-paper-BBQzXsbVnGs</li>
<li>https://pixabay.com/photos/notebook-paper-pages-open-731212/</li>
<li>https://unsplash.com/photos/brown-wooden-toy-blocks-GQ327RPuxhI</li>
<li>https://unsplash.com/photos/macro-shot-of-assorted-insects-on-green-leaf-GGewLGcQD-I</li>
<li>https://unsplash.com/photos/girl-pulling-the-collar-of-dog-during-daytime-cSsvUtTVr0Q</li>
<li>https://unsplash.com/photos/waterfall-at-daytime-waAAaeC9hns</li>
<li>https://nvie.com/posts/a-successful-git-branching-model/</li>
<li>https://unsplash.com/photos/man-in-black-crew-neck-t-shirt-and-beige-pants-sitting-on-white-and-blue-stairs-XY0uyBhZWCA</li>
</ul>

</section>