q2K BHP
Black History Portal
THE BHP WIRE —
HIDDEN TRUTHS
GREENWOOD / BLACK WALL STREET WILMINGTON 1898 LITTLE ROCK NINE TUSKEGEE STUDY ROSEWOOD 1923 THE TUSKEGEE AIRMEN SENECA VILLAGE BLACK TOWNS GREENWOOD / BLACK WALL STREET WILMINGTON 1898 LITTLE ROCK NINE TUSKEGEE STUDY ROSEWOOD 1923 THE TUSKEGEE AIRMEN SENECA VILLAGE BLACK TOWNS
What's New!
THE JOURNEY THROUGH TIME
BHP HOME BEFORE AMERICA 1800–1936 1937–1957 1958–1980 1981–2000 2001–PRESENT

Explore Black History

Explore the people, places, events, achievements, struggles and stories that shaped our journey.

✊🏾

Civil Rights

Movements, leaders, victories and the continuing fight for equality.

⚙️

Black Inventors

Innovation, patents, science, technology and world-changing contributions.

🏆

Sports

Pioneers, champions, Negro Leagues, records, activism and excellence.

♟️

People

Meet the people whose lives, choices and achievements shaped the journey.

📍

Places

Black towns, communities, institutions and places where history happened.

📜

Events

Moments that changed communities, movements, institutions and the nation.

Enter a person, place, event, or topic.
MY'STORY

The MOVE Fire

This is a personal recollection on the Move fire on May 13, 1985 Philadelphia police fired thousands of rounds at the MOVE house, city officials approved dropping an explosive device on the roof, the resulting fire was allowed to burn, 11 people—including five children—died, and 61 homes were destroyed. Philadelphia City Council later called it a “brutal attack carried out by the City of Philadelphia on its own citizens” and acknowledged that no individual faced criminal consequences for the bombing. One timeline correction worth preserving for the BHP record: the major previous MOVE-police confrontation was August 8, 1978, about seven years before the bombing, not a year or two earlier. Officer James Ramp was killed, other police and firefighters were wounded, nine MOVE members were later convicted, and television cameras recorded police beating Delbert Africa during his arrest. The 1985 MOVE Commission later specifically criticized city planners for failing to adequately use lessons from that 1978 confrontation. And that actually strengthens the point you’re making: 1985 did not happen without precedent or institutional memory. There had already been a deadly confrontation with MOVE, years of conflict, negotiations and police involvement before Osage Avenue.

MORE →
BLACK FACTS
The Truths They Never Taught You...

Wilmington 1898 — An American Coup

Wilmington, North Carolina once had a thriving Black middle class and an elected interracial government. In 1898 white supremacists used violence to overthrow that government, kill Black residents and drive many others from the city.

MORE →
BHP gathered finds from its connected research sources. Showing the 4 strongest Black History matches.
← BACK TO RESULTS
Wikipedia

Bug tracking system

"Issue tracker" redirects here. For the types of records used in technical support for customer issues and incident responses, see support ticket.

A bugtracker, bug-tracking system, or defect-tracking system is a software application that keeps track of reported software bugs in software development projects. An item in a bugtracker may be referred to as a bug, which should not be confused with the defect being documented. In contexts where the term "bugtracker" is used, a bugtracker might be considered a specialized type of ticket-tracking system, with "bug" corresponding to a ticket.

Many bug-tracking systems, such as those used by most open-source software projects, allow end-users to enter bug reports directly.[1] Other systems are used only internally in a company or organization doing software development. Typically bug-tracking systems are integrated with other project management software.

A bug-tracking system is usually a necessary component of a professional software development infrastructure, and consistent use of a bug- or issue-tracking system is considered one of the "hallmark of a good software team".[2]

Making

[edit]

A major component of a bug-tracking system is a database that records facts about known bugs. Facts may include the time a bug was reported, its severity, the erroneous program behavior, and details on how to reproduce the bug; as well as the identity of the person who reported it and any programmers who may be working on fixing it.[3]

Typical bug-tracking systems support the concept of the life cycle for a bug which is tracked through the status assigned to the bug. A bug-tracking system should allow administrators to configure permissions based on status, move the bug to another status, or delete the bug. The system should also allow administrators to configure the bug statuses and to what extent a bug in a particular status can be moved. Some systems will e-mail interested parties, such as the submitter and assigned programmers, when new records are added or the status changes.

Usage

[edit]

The main benefit of a bug-tracking system is to provide a clear centralized overview of development requests (including both bugs and improvements; the boundary is often fuzzy), and their state. The prioritized list of pending items (often called backlog) provides valuable input when defining the product road map, or maybe just "the next release".

In a corporate environment, a bug-tracking system may be used to generate reports on the productivity of programmers at fixing bugs. However, this may sometimes yield inaccurate results because different bugs may have different levels of severity and complexity. The severity of a bug may not be directly related to the complexity of fixing the bug. There may be different opinions among the managers and architects.

A local bug tracker (LBT) is usually a computer program used by a team of application support professionals (often a help desk) to keep track of issues communicated to software developers. Using an LBT allows support professionals to track bugs in their "own language" and not the "language of the developers." In addition, an LBT allows a team of support professionals to track specific information about users who have called to complain—this information may not always be needed in the actual development queue. Thus, there are two tracking systems when an LBT is in place.

Part of integrated project management systems

[edit]

Bug and issue-tracking systems are often implemented as a part of integrated project management systems. This approach allows including bug-tracking and fixing in a general product development process, fixing bugs in several product versions, automatic generation of a product knowledge base and release notes.

Distributed bug-tracking

[edit]

Some bug trackers are designed to be used with distributed revision control software. These distributed bug trackers allow bug reports to be conveniently read, added to the database or updated while a developer is offline.[4] Fossil and Veracity both include distributed bug trackers.

Recently, commercial bug-tracking systems have also begun to integrate with distributed version control. FogBugz, for example, enables this functionality via the source-control tool, Kiln.[5]

Although wikis and bug-tracking systems are conventionally viewed as distinct types of software, ikiwiki can also be used as a distributed bug tracker. It can manage documents and code as well, in an integrated distributed manner. However, its query functionality is not as advanced or as user-friendly as some other, non-distributed bug trackers such as Bugzilla.[6] Similar statements can be made about org-mode, although it is not wiki software as such.

Bug-tracking and test management

[edit]

While traditional test management tools such as HP Quality Center and IBM Rational Quality Manager come with their own bug-tracking systems, other tools integrate with popular bug-tracking systems.[citation needed]

See also

[edit]

References

[edit]
  1. ^ Bogomil Shopov (September 8, 2014). "Implement Client-side Bug Reporting". Archived from the original on 13 November 2014. Retrieved 17 November 2014.
  2. ^ Joel Spolsky (November 8, 2000). "Painless Bug Tracking". Retrieved 29 October 2010.
  3. ^ Kaner, Cem (July 2000). "Bug Advocacy" (PDF). kaner.com. pp. 81, 98. Retrieved 2021-05-19.
  4. ^ Jonathan Corbet (May 14, 2008). "Distributed bug tracking". LWN.net. Retrieved 7 January 2009.
  5. ^ "FogBugz Features". Fogbugz.com. Archived from the original on 2013-07-05. Retrieved 2010-10-29.
  6. ^ Joey Hess (6 April 2007). "Integrated issue tracking with Ikiwiki". NetworkWorld.com. IDG. Retrieved 10 November 2014.
[edit]

Source: Wikipedia. Article content is retrieved live through the MediaWiki API.

No preview image
Wikipedia

Bug tracking system

A bugtracker, bug-tracking system, or defect-tracking system is a software application that keeps track of reported software bugs in software development projects. An item in a bugtracker may be referred to as a bug, which should not be confused with the defect being documented. In contexts where the term "bugtracker" is used, a bugtracker might be considered a specialized type of ticket-tracking system, with "bug" corresponding to a ticket. Many bug-tracking systems, such as those used by most open-source software projects, allow end-users to enter bug reports directly. Other systems are used only internally in a company or organization doing software development. Typically bug-tracking systems are integrated with other project management software. A bug-tracking system is usually a necessary component of a professional software development infrastructure, and consistent use of a bug- or issue-tracking system is considered one of the "hallmark of a good software team".

MORE →
No preview image
Wikipedia

Mantis Bug Tracker

Mantis Bug Tracker is a free and open source, web-based bug tracking system. The most common use of MantisBT is to track software defects. However, MantisBT is often configured by users to serve as a more generic issue tracking system and project management tool. The name Mantis and the logo of the project refer to the insect family Mantidae, known for tracking and feeding on other insects, colloquially referred to as "bugs". The name of the project is abbreviated to either MantisBT or just Mantis.

MORE →
Wikipedia

Bugzilla

Bugzilla is a web-based general-purpose bug tracking system and testing tool originally developed and used by the Mozilla project, and licensed under the Mozilla Public License. Released as open-source software by Netscape Communications in 1998, it has been adopted by a variety of organizations for use as a bug tracking system for both free and open-source software and proprietary projects and products. Bugzilla is used, among others, by the Mozilla Foundation, WebKit, Linux kernel, FreeBSD, KDE, Apache and LibreOffice. Red Hat uses it, but is gradually migrating its product to use Jira. It is also self-hosting.

MORE →
Wikipedia

Fossil (software)

Fossil is a software configuration management, bug tracking system and wiki software server for use in software development created by D. Richard Hipp.

MORE →
TOPIC OF THE DAY

Greenwood / Black Wall Street

Before the 1921 destruction of Tulsa’s Greenwood District, Black residents had created a remarkable center of business and community life. The district included stores, professional offices, entertainment venues and homes owned by Black citizens. Understanding Greenwood means learning what was built—not only what was burned.

MORE →
TRIVIA QUESTION OF THE DAY

Which heavyweight champion was known as the “Brown Bomber”?

Joe Louis.