Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://www.chromium.org/for-testers/bug-reporting-guidelines below:

Bug Life Cycle and Reporting Guidelines

1. Important links
   1. Chromium (the web browser)
   2. Chromium OS (the operating system)
2. Bug reporting guidelines
3. Release block guidelines
4. Triage guidelines
5. Hotlists
6. Status
7. Bug life cycle
8. Helping with bug triage

• Report bugs at https://issues.chromium.org/new
• Specifically:
  • Instructions for reporting crashes.
  • View existing bugs at https://issues.chromium.org/issues?q=status:open

• Report bugs at Chromium Issue Tracker
• View existing bugs at Chromium OS issues

You need a Google Account associated with your email address in order to use the bug system.

• If you're a web developer, see How to file a good bug
• Make sure the bug is verified with the latest Chromium (or Chrome canary) build.
• If it's one of the following bug types, please provide some further information:
  • Web site compatibility problem: Please provide a URL to replicate the issue.
  • Hanging tab: See Reporting hanging tab bugs.
  • Crash: See Reporting crash bugs.
• Provide a high-level problem description.
• Mention detailed steps to replicate the issue.
• Include the expected behavior.
• Verify the bug in other browsers and provide the information.
• Include screenshots, if they might help.
• If a bug can be reduced to a simplified test, then create a simplified test and attach it to the bug.
• Additional Bug Reporting Guidlines for the Mac & Linux builds.
• Additional Guidelines for Reporting Security Bugs.

• Release Block Guidelines

• Triage Best Practices

Hotlists are used to help the engineering team categorize and prioritize the bug reports that are coming in. Each report can (and should) have multiple hotlists.

For details on hotlists used by the Chromium project, see Chromium Bug Hotlists.

To better understand the various fields and statuses, please visit: Issues Overview

• When a bug is first logged, it is given New status.
• The Unconfirmed hotlist is removed when the bug has been verified as a Chromium bug.
• Once a bug has been picked up by a developer, it is marked as Assigned.
• A status of In Progress (Accepted) means a fix is being worked on.
• A status of Fixed means that the bug has been fixed, and Verified means that the fix has been tested and confirmed. Please note that it will take some time for the "fix" to make it into the various channels (canary, beta, release) - pay attention to the milestone attached to the bug, and compare it to chrome://version.
• A bug on the Unconfirmed hotlist is a newly logged bug that hasn't been confirmed
• A bug on the Available hotlist has been triaged and is waiting for a fix.

Read https://www.chromium.org/getting-involved/bug-triage if you're interested in helping with bug triage.

Infrastructure and build tools

If you find an issue with our infrastructure or build tools, please file the ticket using the Build Infrastructure template:

• https://code.google.com/p/chromium/issues/entry?template=Build Infrastructure

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4