Translation

(itstool) path: info/title
Problem Report Handling Guidelines
44/340
Context English Spanish State
_
translator-credits
Sergio Carlavilla carlavilla@FreeBSD.org, 2019
Problem Report Handling Guidelines
Guía para el manejo de informes de problemas
FreeBSD is a registered trademark of the FreeBSD Foundation.
FreeBSD is a registered trademark of the FreeBSD Foundation.
Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the <quote>™</quote> or the <quote>®</quote> symbol.
Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the <quote>™</quote> or the <quote>®</quote> symbol.
$FreeBSD: head/en_US.ISO8859-1/articles/pr-guidelines/article.xml 51348 2017-12-30 22:56:56Z eadler $
$FreeBSD$
These guidelines describe recommended handling practices for FreeBSD Problem Reports (PRs). Whilst developed for the FreeBSD PR Database Maintenance Team <email>freebsd-bugbusters@FreeBSD.org</email>, these guidelines should be followed by anyone working with FreeBSD PRs.
Esta guía describe las prácticas recomendadas para manejar los informes de problemas (PRs) de FreeBSD. Aunque se desarrolló para el FreeBSD PR database maintenance team <email>freebsd-bugbusters@FreeBSD.org</email>, cualquiera que trabaje con PRs de FreeBSD debe seguir estas pautas.
<personname><firstname>Dag-Erling</firstname><surname>Smørgrav</surname></personname>
<personname><firstname>Dag-Erling</firstname><surname>Smørgrav</surname></personname>
<personname><firstname>Hiten</firstname><surname>Pandya</surname></personname>
<personname><firstname>Hiten</firstname><surname>Pandya</surname></personname>
Introduction
Introducción
Bugzilla is an issue management system used by the FreeBSD Project. As accurate tracking of outstanding software defects is important to FreeBSD's quality, the correct use of the software is essential to the forward progress of the Project.
Bugzilla es un sistema de gestión de errores utilizado por el proyecto FreeBSD. Un seguimiento preciso de los defectos de software pendientes es importante para la calidad de FreeBSD, el uso correcto del software es esencial para el progreso del proyecto.
Access to Bugzilla is available to the entire FreeBSD community. In order to maintain consistency within the database and provide a consistent user experience, guidelines have been established covering common aspects of bug management such as presenting followup, handling close requests, and so forth.
El acceso a Bugzilla está disponible para toda la comunidad de FreeBSD. Con el fin de mantener la coherencia dentro de la base de datos y proporcionar una experiencia de usuario consistente, se han establecido pautas que cubren aspectos comunes de la gestión de errores, como la presentación del seguimiento, el manejo de las solicitudes de cierre, etc.
Problem Report Life-cycle
Ciclo de vida de un informe de problemas
The Reporter submits a bug report on the website. The bug is in the <literal>Needs Triage</literal> state.
El usuario envía un informe de error al sitio web. El error está en el estado <literal>Needs Triage</literal>.
Jane Random BugBuster confirms that the bug report has sufficient information to be reproducible. If not, she goes back and forth with the reporter to obtain the needed information. At this point the bug is set to the <literal>Open</literal> state.
Jane Random BugBuster confirma que el error reportado tiene la suficiente información para ser reproducido. Si no, se interactuará repetidamente con el usuario para obtener la información necesaria. En este punto, el error se establece en el estado <literal>Open</literal>.
Joe Random Committer takes interest in the PR and assigns it to himself, or Jane Random BugBuster decides that Joe is best suited to handle it and assigns it to him. The bug should be set to the <literal>In Discussion</literal> state.
Joe Random Committer se interesa por el PR y se lo asigna a si mismo, o Jane Random BugBuster decide que Joe es la persona más adecuada para resolver el problema y le asigna error. El error se debe poner en el estado <literal>In Discussion</literal>.
Joe has a brief exchange with the originator (making sure it all goes into the audit trail) and determines the cause of the problem.
Joe tiene una breve conversación con el usuario que ha enviado el informe del problema (asegurándose de que todo queda registrado) y determina la causa.
Joe pulls an all-nighter and whips up a patch that he thinks fixes the problem, and submits it in a follow-up, asking the originator to test it. He then sets the PRs state to <literal>Patch Ready</literal>.
Joe está toda la noche trabajando y elabora un parche que cree que soluciona el problema, y lo envía en un follow-up, pidiéndole al usuario que lo ha enviado que lo pruebe. A continuación, fija el estado del PR en <literal>Patch Ready</literal>.

Loading…

User avatar None

New source string

FreeBSD Doc / articles_pr-guidelinesSpanish

New source string 11 months ago
Browse all component changes

Glossary

English Spanish
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: info/title
Labels
No labels currently set.
Source string location
article.translate.xml:5
Source string age
11 months ago
Translation file
articles/es_ES/pr-guidelines.po, string 2