Joomla! Documentation™

Este artículo documenta el proceso actual de seguimiento de fallos en Joomla!. Desde el momento en que se informa de un nuevo fallo hasta que se cierra este informe.

Los fallos en Joomla! se gestiona en el Gestor de incidencias de Joomla!, Este gestor de incidencias es para fallos relacionados con las versiones de Joomla! soportadas. La versión recomendada es J3.10.

Ayudando

No tienes que ser un miembro del Equipo de Errores de Joomla! para ayudar a arreglar fallos en Joomla. Cualquiera puede informar de fallos, probar correcciones o enviar correcciones. Si quieres ayudar resolviendo fallos, ve al Gestor de incidencias. Puedes resolver las incidencias abiertas tal y como se detalla a continuación. Puedes crear y enviar correcciones para los fallos Confirmados. O puedes ayudar a probar incidencias Pendientes. Para informar sobre lo que has hecho, accede con una cuenta de Github y añade un comentario. Te sorprenderá cuánto impacto puedes tener y lo bien que se siente al contribuir al proyecto Joomla! Si tienes alguna pregunta o si estás interesado en unirte al JBS, por favor contacta con Los Coordinadores el equipo de fallos.

Probando Pre lanzamientos

Before a stable release of Joomla is released the update needs testing. This is a simple process:

1. Install the Staging release of Joomla https://github.com/joomla/joomla-cms in a subfolder or on localhost (you can use a copy of a production site but never test on a live production site).
2. Navigate to the Options of the Joomla! Update component and set the 'Update server' to 'Test'. Components Joomla Update
3. When a Joomla pre release is ready for testing, log into your test site and install the Update. Then test the site works as expected. Please report any errors/bugs on the Joomla! Issue Tracker

Informando de fallos

El proceso comienza normalmente de una de dos formas: el fallo se añado al gestor de incidencias respectivo o un usuario informa del fallo en el Foro de fallos de Joomla! para la versión de mantenimiento correspondiente.

Problemas informados en el foro

JBS members scan the forums to determine when issues need to be put into the tracker. If the issue can be reproduced, is clearly a bug, and there are step-by-step instructions for how to reproduce it, it can be entered into the tracker with a status of Confirmed. If it is not as clear-cut, it can be entered with a status of Open, so that other JBS members will know it needs further investigation.

Issues directly reported to the tracker

When an issue is added to the tracker, the status could be depending on the situation;

1. New
2. Confirmed
3. Pending

If the issue needs more investigation, then it should be set to New. If the issue (1) is a bug and (2) can be reproduced and (3) has good test instructions, it should be set to Confirmed. If it meets the three Confirmed criteria and also has a good patch attached, it should be set to Pending. See below for more information about the status codes.

Issue Priorities

Why most issues are priority 3, or Medium. The artifacts are prioritized according to the following characteristics:

Critical (1): The trunk is not working at all. Significant parts of the source are broken preventing key operations. Examples would be login, installation, extension installers, javascript errors that prevent you from moving a save or similar action, etc. Also includes the generation of Fatal PHP errors and major security issues in a prerelease (Security issues for a stable release should NOT be reported in the tracker but instead reported to the security team security@joomla.org).

Urgent (2): Parts of the source are obstructing operation in a serious way or causing a major loss in advertised function. Examples would includes PHP notices and warnings and reported javascript errors. Major issues will also typically prevent the release cycle from moving from Beta to Release Candidate (RC), or Release Candidate to General Availability (GA).

Medium (3): Issues that are hindering advertised behavior but the application is still workable. Examples would include parameters not working as advertised, language files not loading as expected, etc.

Low (4): Minor loss of function and generally annoying behavior. May include less common platform or browser specific problems that while they may be technically major in those environments, they represent a minority. Also include missing translation strings.

Very low (5): Cosmetic problems, misspelled words, graphically misaligned object, less common issues with parameters, etc.

Resolving Issues

The bug squad takes care of the Joomla releases. For example, that means getting the 3.4, 3.5, ... etc releases ready by fixing problems that come up. The idea is to make the release increasingly stable and take care of issues that come up. At the same time, it is vitally important not to break anything that is working. That's called software regression and it's not something you want at this stage. In the trackers there are several common statuses, mainly: new, confirmed, pending, ready to commit.

• New means it's reported, but it hasn't been determined for sure whether it is a real bug or not. Many Open issues are not actually bugs. If the issue fits into one of the categories below, then the status is changed as indicated and the bug is closed:
  • Cannot be reproduced. We have tried the same thing the reported did but the software appears to work correctly. (In many cases, more information is needed to be able to reproduce a bug. See "Information Required" below.) Change status to Unconfirmed Report.
  • Has already been reported in a different issue number. Change status to Duplicate report and add the number on the duplicates tab.
  • Is a known limitation of the software. Change status to Known issue.
  • Is a feature request, a mistake made by a user, or is the way the software is intended to work. Change status to Expected Behaviour.
  • Is a bug with an extension or some other external program or a server issue that will not be addressed. Change status to Closed and leave a comment explaining the reason.
• Information Required is used if we need more information from the person who reported the issue to decide about the issue. For example, there are questions about how to reproduce the problem or other questions about the issue. If we get the information we need, then we can continue processing the issue. If we don't get the information within two weeks, then we can change the status to Unable to confirm (or another of the closed status codes if that is more applicable).
• Needs Review is used if we need a PLT Member or CMS Maintainer for a review / decision. This is different from Information Required, which means that we need more information from the person who reported the issue.
• Confirmed means that JBS has confirmed that this issue is a bug in Joomla! that should be fixed. That's when the JBS tries to solve it or consults with the development team about a solution. At this point there should be clear step-by-step test instructions that indicate how to reproduce the problem.
• Pending means that a patch has been submitted. Every Pending issue should have instructions that tell the tester how to reproduce the problem and make sure the patch fixes the problem.
• Ready to commit means that (in general) two separate people have successfully tested the same patch file, and it works correctly with the patch. Note that, for some issues that are more complex or higher impact, we may need more than two people to test or may need to test on multiple platforms. For simple issues, such as fixing typos in language strings or comments, one tester is enough.
• Fixed in Code Base means that, after reviewing the code, the JBS commit coordinators have determined that the patch is good and the change has been committed to the Joomla! code-base. At this point, it will be part of the next Joomla! maintenance release.

The Easy Test-mark is not a dedicated status, it is more a label to show Pending issues with easy test instructions.

The flowchart below provides a visual guide to how the process for resolving bugs works.