Skip to content

[5.4] Docs: Add a PR targeting section to the README #46471

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 6 commits into
base: 5.4-dev
Choose a base branch
from
Open

[5.4] Docs: Add a PR targeting section to the README #46471

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
bb91b83
[5.4] docs: Add guidelines for Pull Request target branches
LadySolveig Nov 19, 2025
63ffa37
[5.4] docs: Add guidelines for Pull Request target branches
LadySolveig Nov 19, 2025
c6c8798
docs:Clarify bug classification and target branches footnote
LadySolveig Nov 19, 2025
cb8656c
docs: Add target branch links
LadySolveig Nov 19, 2025
90f49a3
docs: Clarify bug target branches
LadySolveig Nov 19, 2025
863fcda
docs: Update target branch links
LadySolveig Nov 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,6 +74,21 @@ Do you want to improve Joomla?
* Documentation for [Web designers](https://docs.joomla.org/Special:MyLanguage/Web_designers).
* Provide a translation for Joomla: [Joomla Crowdin Project](https://joomla.crowdin.com/cms)

Which branch should my Pull Request target?
--------------------
Using a simple classification keeps the project **stable**, **transparent**, and **easy** for everyone to contribute.

| Type of change | What it means | Target branch |
|---|---|---|
| **Bug / Patch release** | The change fixes an actual error. The software crashes, produces the wrong result, or behaves contrary to its specification. It can be resolved without large‑scale refactoring or new functionality. | **[5.4-dev](https://github.com/joomla/joomla-cms/tree/5.4-dev)** (6.0-dev) **\*** |
| **Feature / Minor release** | Anything that isn’t a strict bug – new behavior, refactoring, performance improvements, enhancements, UI tweaks, etc. These changes are bundled together for the next minor version. | **[6.1-dev](https://github.com/joomla/joomla-cms/tree/6.1-dev)** |

**\*** All bugs that already exist in version 5.4.x should be fixed in `5.4-dev`. Only bugs that are introduced for the first time in version 6.0.x should target the [`6.0-dev`](https://github.com/joomla/joomla-cms/tree/6.0-dev) branch.

A member of the maintainer or bug squad team confirms the classification and sets the appropriate labels when a PR is opened. If a PR is opened in the wrong branch, a maintainer will simply ask you to retarget it to the proper branch.



Copyright
---------------------
* (C) 2005 Open Source Matters, Inc. <https://www.joomla.org>
Expand Down