diff options
Diffstat (limited to 'Documentation/workflow')
-rw-r--r-- | Documentation/workflow/IssuesFeedbackEngagement.md | 12 | ||||
-rw-r--r-- | Documentation/workflow/OfficalAndDailyBuilds.md | 2 |
2 files changed, 9 insertions, 5 deletions
diff --git a/Documentation/workflow/IssuesFeedbackEngagement.md b/Documentation/workflow/IssuesFeedbackEngagement.md index a6c0550e08..f83b2b6a89 100644 --- a/Documentation/workflow/IssuesFeedbackEngagement.md +++ b/Documentation/workflow/IssuesFeedbackEngagement.md @@ -3,10 +3,14 @@ ## Reporting Problems (Bugs) -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. +We track bugs, feature requests and other issues in repository where they will get ultimately fixed. If you have a problem and +believe that the issue is in CoreCLR itself (native runtime or System.Private.CoreLib base level class library) you should +log it on the [CoreCLR Issues Page](https://github.com/dotnet/coreclr/issues). If in the upper levels of the class library +use the [CoreFX Issues Page](https://github.com/dotnet/corefx/issues). For all managed API addition proposals use +the [CoreFX Issues Page](https://github.com/dotnet/corefx/issues) and follow +the [API Review Process](https://github.com/dotnet/corefx/blob/master/Documentation/project-docs/api-review-process.md). + +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. ### NET Forums If you want to ask a question, or want wider discussion (to see if others share you issue), we encourage you to start a thread diff --git a/Documentation/workflow/OfficalAndDailyBuilds.md b/Documentation/workflow/OfficalAndDailyBuilds.md index 5a36af6f46..d5efb93c04 100644 --- a/Documentation/workflow/OfficalAndDailyBuilds.md +++ b/Documentation/workflow/OfficalAndDailyBuilds.md @@ -1,7 +1,7 @@ # Official Releases and Daily Builds of CoreCLR and CoreFX components If you are not planning on actually making bug fixes or experimenting with new features, then you probably -don't need to don't need build CoreCLR yourself, as the .NET Runtime team routinely does this for you. +don't need to build CoreCLR yourself, as the .NET Runtime team routinely does this for you. Roughly every three months, the .NET Runtime team publishes a new version of .NET Core to Nuget. .NET Core's official home on NuGet is |