From: Dan Moseley Date: Wed, 16 Nov 2016 21:13:22 +0000 (-0800) Subject: Update IssuesFeedbackEngagement.md X-Git-Tag: submit/tizen/20210909.063632~11030^2~8878 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=57aba5ee04bbc6a8f647c4630cca66c44d9b032c;p=platform%2Fupstream%2Fdotnet%2Fruntime.git Update IssuesFeedbackEngagement.md Commit migrated from https://github.com/dotnet/coreclr/commit/124754f2f5382f2781db8f132e3c89d21b56600b --- diff --git a/docs/coreclr/workflow/IssuesFeedbackEngagement.md b/docs/coreclr/workflow/IssuesFeedbackEngagement.md index e9068c7..a6c0550 100644 --- a/docs/coreclr/workflow/IssuesFeedbackEngagement.md +++ b/docs/coreclr/workflow/IssuesFeedbackEngagement.md @@ -3,9 +3,8 @@ ## Reporting Problems (Bugs) -We track bugs, feature requests and other issues on the .NET Core's [Issues Page](https://github.com/dotnet/coreclr/issues). -If you have a problem and believe that the issue is in .NET Core itself (native runtime or base level class library) -you should log it there. If in the upper levels of the class library the [CoreFX Issues Page](https://github.com/dotnet/corefx/issues). +We track bugs, feature requests and other issues [in this repo](https://github.com/dotnet/coreclr/issues). +If you have a problem and believe that the issue is in the native runtime you should log it there. If in the managed code log it in the [CoreFX repo](https://github.com/dotnet/corefx/issues) _even if the code is in this CoreCLR repo_ (ie., in mscorlib/System.Private.Corelib). The reason for this is we sometimes move managed types between the two and it makes sense to keep all the issues together. Before you log a new issue, you should try using the search tool on the issue page on a few keywords to see if the issue was already logged.