Joomla! Developer Network
There is always a great deal of Joomla! development activity underway and communicating with other developers in the community is essential. This site is a resource for anyone looking to build or maintain software based on the Joomla platform
While we strive to be as efficient as possible, there are times when things don't go smoothly, causing stress and headaches for our user base and the community members who test and prepare our releases. This last week has been an example of some rough times for our releases, and though no single person or group is to blame for any of the issues that we've experienced with these last releases, they do highlight areas where our teams and workflows can improve.
The Joomla PLT is happy to announce that contributions to the CMS will no longer require a JoomlaCode tracker item. We’re now ready to start using our brand new issue tracker issues.joomla.org.
New bug reports and feature requests should be created either at issues.joomla.org or directly on GitHub. Code contributions made via Github will automatically create the issue for you (no more duplication required). All outstanding JoomlaCode items will require a corresponding Github issue.
Due to technical limitations of the JoomlaCode software, we cannot disable the JoomlaCode tracker for just the Joomla CMS project. We ask that contributors stop using it immediately to create new issues or comment on existing issues. We will make all the necessary process changes to reinforce that.
NOTE: This change will not have any impact on other projects using JoomlaCode.org.
Easing the contribution process
Ok, so there’s been some questions about Joomla 3.4, the next big release for Joomla. I’m quite excited to be able to be a part of this release and we have some great things planned. Timelines are always the first thing people want to know; followed closely with what features will be available. In this particular release there are some additional new terms being used which may be helpful to define. Three quick topics, let’s discuss each in order.
An Update on Joomla 3.4
Have some questions that you’ve just got to get answered? The chances are good we've already done it. Check the FAQ below:
For those who love detail - you can see the full development strategy here
For those of you who want the quick, simple to understand overview - read here.
Q: Will 3.5 be the LTS release for the 3.x series?
A: No. The strategies have been modified to not lock in a specific release as the LTS release of a series. Under the revised strategy, unless superseded with a newer minor release, there will be at least two years of support for the last minor release of a series. The concept of an LTS release is being eliminated in favor of this. For example, if 3.4 were to be the final minor release of the 3.x series, it would be supported for at least two years after its release.
FAQ's for Joomla's Improved Release Cycle
Have questions? You can ask us on Twitter
To help answer questions of the development and release cycle of for Joomla 3, we've created a twitter account to help! Ask a question to @askjoomla by sending a tweet. Questions will be updated here daily so you can keep your Joomla! businesses running smoothly.
This strategy document sets out what the community of Joomla users, from ordinary non-technical users through to high-level technical developers, can expect from the products that come under the umbrella of the Joomla project.
This is primarily about how we approach and manage change: how we adapt, develop and grow our products in an ever-changing technological landscape; how we communicate to our users and contributors what to expect from our products as they change from one release to the next; and how we guide our contributors towards making the future changes that we want as a community.
The stakeholders in our project have widely varying needs and a balance must be struck between, at one extreme, those for whom any change is unwelcome and all shades to the other extreme of those who thrive on continuous change. Change is essential if our products are to remain relevant to their intended users, so our goal is to manage that change in such a way that we minimise the disruption it can cause.
Since the Joomla project is responsible for more than one product, this strategy is written to be as generic as possible and to allow new products to be added to our portfolio without forcing any extensive re-writes.
This strategy builds on the substantial practical experience of a lot of people over the many years since the project's foundation. The reasoning behind what is written here, and the lessons learned in leading up to it, is outside the scope of the document itself and reference should be made to other sources for that commentary.
Joomla! Development Strategy