Label Glossary

Description of the GitHub labels used by ChakraCore

Accepting PRs

• We welcome a 3rd party pull request for this issue. It is specifically well suited for outside contributors and is up for grabs. (Other issues are okay for 3rd party PRs, but in any case, please indicate that you're claiming an issue to reduce duplication of effort.) See also: Your first PR.

APIs

• Issue is related to JSRT APIs (the APIs used to embed ChakraCore in other applications).

Build Break

• Issue is related to a broken build (e.g. compile errors, failing tests).

Bug

• Issue is a bug in ChakraCore.

Bug / Build Bug

• Issue is a bug with the ChakraCore build definitions or infrastructure (does not include compile errors caused by changes to ChakraCore sources). Infrastructure can include our build scripts, Jenkins definitions, or Jenkins infrastructure itself (CC @mmitche for Jenkins infrastructure issues).

Bug / Test Bug

• Issue is a bug in Test or Test infrastructure of ChakraCore (does not include test failures due to actual code defects). Bugs in tests themselves are considered Bugs.

By Design

• Issue raised is actually by design.

Committed

• We are committed to resolving this issue.

Compatibility

• Issue is related to an compatibility between engines, which may or may not be formally specified by the ES spec.

Continuous Integration

• Involves changes to the Jenkins Continuous Integration (Jenkins CI) configuration or related files. May result in temporary CI breaks while the changes propagate. May need special attention from a project or tool maintainer.

Discussion

• Issue is a conversation without a clear, actionable problem or proposal.

Duplicate

• Issue has already been reported in another issue.

ECMAScript Spec

• Issue is actually related to the ES specification rather than ChakraCore itself.

ES Spec Changed

• This issue came up because the ECMAScript Spec changed and the code now needs to be updated to be compliant with the Spec.

External

• Issue is not directly related to ChakraCore but has to do with a related project.

External Contributor

• Pull Request is from an External Contributor and should be assigned to a team member.

Fixed

• Issue has been fixed.

Linux

• Issue related to the Linux cross-platform port.

Merged

• The change has been merged in, but for some reason was not automatically closed as merged by GitHub, so we had to close the issue manually.

Needs More Info

• Issue sounds legitimate but needs more information to be actionable.

Needs Proposal

• Issue is a feature request or architecture design suggestion but not a formal proposal.

NoRepro

• Unable to reproduce the issue described. There is no further action to be taken.

Out of Scope

• Issue is Out of Scope for the ChakraCore project. This may be because it is a feature better implemented in a host, among other reasons.

Pending TC39 Consensus

• Issue is a ECMAScript compliance bug but requires TC39 consensus before action is taken to address it in ChakraCore.

Performance

• Issue is related to run-time performance of ChakraCore.

Proposal

• Issue is a formal proposal.

Question

• Issue is actually a question rather than a problem or proposal.

Suggestion

• Issue is a suggested feature or change but is not a formal proposal.

Task

• Issue has a clear, actionable task.

Waiting

• Waiting on changes from another issue or project.

Wiki

• Issue is related to Wiki content.

Won't Fix

• Issue will not be fixed.

Your first PR

• Issue is well suited to for people new to GitHub contributions -- we're here to help you get started in OSS. These issues are typically limited in scope and impact and thus are good starting points to become familiar with being a contributor to ChakraCore. See also: Accepting PRs.