-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Label Glossary
Doug Ilijev edited this page Jan 28, 2016
·
40 revisions
Description of the GitHub labels used by ChakraCore
- 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.
- Issue is a bug in ChakraCore.
- Issue raised is actually by design.
- We are committed to resolving this issue.
- 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.
- Issue is a conversation without a clear, actionable problem or proposal.
- Issue has already been reported in another issue.
- Issue is actually related to the ES specification rather than ChakraCore itself.
- This issue came up because the ECMAScript Spec changed and the code now needs to be updated to be compliant with the Spec.
- Issue is not directly related to ChakraCore but has to do with a related project.
- Issue has been fixed.
- Issue related to the Linux cross-platform port.
- 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.
- Issue sounds legitimate but needs more information to be actionable.
- Issue is a feature request or architecture design suggestion but not a formal proposal.
- Issue is a ECMAScript compliance bug but requires TC39 consensus before action is taken to address it in ChakraCore.
- Issue is a formal proposal.
- Issue is actually a question rather than a problem or proposal.
- Issue is a suggested feature or change but is not a formal proposal.
- Issue has a clear, actionable task.
Test (omitted)
- We are deliberately omitting this label because issues of this category generally fit into either Task or Bug. Labeling something as Test causes developers to de-prioritize the issues, even if they would otherwise be regarded as important.
- Issue will not be fixed.
- 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.
- Architecture Overview
- Building ChakraCore
- ChakraCore Code Structure
- Contributor Guidance
- Engineering Notes
- Embedding ChakraCore
- Testing ChakraCore
- Getting ChakraCore binaries
- Label Glossary
- Resources
- Roadmap / Release Notes
Want to contribute to this Wiki? Fork it and send a pull request!