Issues found within and using Bash on Ubuntu on Windows
Latest commit 6b4dfb3 Jan 16, 2017 @ivuk ivuk committed with benhillis Typo fixes (#1601)
* Fix a typo in CONTRIBUTING.md

* Fix a typo in README.md, remove a trailing space
Permalink
Failed to load latest commit information.
CONTRIBUTING.md Typo fixes (#1601) Jan 16, 2017
ISSUE_TEMPLATE.md Update ISSUE_TEMPLATE.md Sep 8, 2016
README.md Typo fixes (#1601) Jan 16, 2017

README.md

This repo is for the reporting of issues found within and when using Bash on Ubuntu on Windows.

  • Do not open Github issues for Windows crashes (BSODs) or security issues. Please direct all Windows crashes and security issues to secure@microsoft.com. Issues with security vulnerabilities may be edited to hide the vulnerability details.

Labels

This and our User Voice page are your best ways to interact directly with the Bash on Ubuntu on Windows teams. We will be monitoring and responding to issues as best we can. Please attempt to avoid filing duplicates of open or closed items when possible. In the spirit of openness we will be tagging issues with the following:

  • bug – We consider this issue to be a bug internally. This tag is generally for bugs in implemented features, or something we consider to be a “bug level” change. Things marked with Bug have a corresponding bug in on Microsoft’s internal bug tracking system.

    • Example: No internet connectivity in Bash (#5)
  • feature – Denotes something that is not yet implemented. The community should use our User Voice page for voting on which features everyone feels as the most important. The team will take the User Voice page as input in deciding what to work on next.

    • Example: Docker is not working (#85)
  • discussion – Denotes a discussion on the board that does not relate to a specific feature.

    • Example: Windows Subsystem for Linux is not open source (#178)
  • fixinbound – When possible, we will mark bugs that have been fixed internally. Unfortunately we cannot say specifically when the bug will hit the insider flights.

  • bydesign – Denotes that an issue is raised that we consider is working as intended. We will give some reasoning why this is by design. After one week we will either close the issue or mark as Discussion depending on what comes up.

Additional tags may be used to denote specific types of issues. These include items such as network or symlink.

Closing

Issues may be closed by the original poster at any time. We will close issues if:

  • One week passes after the change goes out to the Insider Fast ring
  • An issue is clearly a dup of another. The duplicate will be linked
  • Any discussion that has clearly run its course

Microsoft Links

Community Links

Troubleshooting

Common troubleshooting issues and solutions are available on our MSDN documentation.