| Actions | PHP | Node | npm |
|---|---|---|---|
Joomla is not installable out of the box from this repository, please use: - For the latest stable package: https://downloads.joomla.org - For a nightly package: https://developer.joomla.org/nightly-builds.html
For detailed instructions please visit https://guide.joomla.org/user-manual/hosting/local-environment-setup
You will need: - PHP - basically the same as you need for running a Joomla Site, but you need the cli (command line interface) Version (see https://docs.joomla.org/Special:MyLanguage/Configuring_a_LAMPP_server_for_PHP_development) - Composer - for managing Joomla's PHP Dependencies. For help installing composer please read the documentation at https://getcomposer.org/doc/00-intro.md - Node.js - for compiling Joomla's Javascript and SASS files. For help installing Node.js please follow the instructions available on https://nodejs.org/en/ - Git - for version management. Download from here https://git-scm.com/downloads (MacOS users can also use Brew and Linux users can use the built-in package manager, eg apt, yum, etc).
Steps to setup the local environment: - Clone the repository:
git clone https://github.com/joomla/joomla-cms.git
cd joomla-cms
git checkout 6.2-dev
composer install
npm ci
Things to be aware of when pulling:
Joomla creates a cache of the namespaces of its extensions in JOOMLA_ROOT/administrator/cache/autoload_psr4.php. If
extensions are created, deleted or removed in git then this file needs to be recreated. You can simply delete the file
and it will be regenerated on the next call to Joomla.
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. | 6.2-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.3-dev |
* All bugs that already exist in version 5.4.x or 6.1.x or 6.2.x should be fixed in 6.2-dev.
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.
| 日期 | 榜单 | 排名 | 周期新增 | 总 STAR |
|---|