Repo sync for protected CLA branch

docs/ide/how-to-report-a-problem-with-visual-studio.md

@@ -15,105 +15,77 @@ ms.workload:
 > [!NOTE]
 > For Visual Studio for Mac, see [How to report a problem in Visual Studio for Mac](/visualstudio/mac/report-a-problem).
 
-You can report a problem from either Visual Studio or its installer by using the Feedback Tool included in them. The Feedback Tool enables you to easily include diagnostic information in your feedback and helps Visual Studio teams to diagnose and fix issues much more effectively. Here are the steps to report a problem.
+You can report a problem from either Visual Studio or its installer. The built-in Feedback Tool allows you to easily add diagnostic information that helps the Visual Studio teams diagnose and fix the issues. Here are the steps to report a problem.
 
 1. **In Visual Studio**, select the feedback icon in the upper-right corner and select Report a Problem. You can also access the feedback tool  from the menu **Help** > **Send Feedback** > **Report a Problem**.
-![Report an issue pop-up on Visual Studio Developer Community](media/vsfeedbackentry.png)
+![Report an issue pop-up on Visual Studio Developer Community](media/feedback-button.png)
 Alternatively, report a problem in **Visual Studio Installer** if you can't install Visual Studio or are unable to access the feedback tool within Visual Studio.  In the Installer, select the feedback icon in the upper-right corner and select Report a Problem.
 ![Report an issue pop-up on Visual Studio Developer Community](media/installer.png)
 
-1. If not signed in, select **Sign In** as shown in the following screenshot. Follow the instructions on-screen to sign in.
+1. Clicking **Report a Problem** will open your default browser and sign you in using the same account you use to sign in to Visual Studio
 
-   ![Sign in to report a problem](../ide/media/sign-in-new-ux.png)
+   ![Sign in to report a problem](../ide/media/feedback-browser-top.png)
 
-   Not only can you report a problem when you are signed in, but you can also vote and comment on any existing feedback.
+1. Start by entering the descriptive title of your bug report. It must be at least 25 characters long.
 
-1. Once signed in, you will be able to see your **Problems** and **Activity** on the **Items I follow** screen
+    ![Report a problem](../ide/media/feedback-report.png)
 
-   ![Items I Follow](../ide/media/items-i-follow.png)
+1. Once you start typing, possible duplicates are shown under the title field
 
-1. Visual Studio provides an interface to search for your problem and see if others have reported it. If someone has reported it, "up-vote" it to let us know.
-   > [!NOTE]
-   > In order to search, please input the desired text into the search box and either click Enter or press the Search icon.
+    ![Search for duplicates](../ide/media/feedback-search.png)
 
-   ![Search and vote for similar problems](../ide/media/search-and-vote.png)
+1. Select the possible duplicate bug reports to see if there is one matching your own problem. If there is, vote for it instead of creating your own ticket.
 
-1. If you don't find the problem you encountered, choose **Report new problem** at the bottom of the screen.
+    ![Vote for duplicates](../ide/media/feedback-duplicate.png)
 
-1. Create a descriptive title for the problem that helps us route it to the correct Visual Studio team.
+2. If no duplicates were found, continue by entering a description of the problem. It's important to be as clear as possible to increase the chances of us being able to reproduce the bug. Make sure to include clear reproduction steps.
 
-1. Give us any additional details, and if possible, provide us with the steps to reproduce the problem.
+3. If relevant to the bug report, take a screenshot by checking the *Include Visual Studio screenshot* checkbox.
 
-   ![Report a new problem](../ide/media/report-new-problem.png)
+    ![Take a screenshot](../ide/media/feedback-screenshot.png)
+    *Only Microsoft engineers can see the screenshot*
 
-1. Select **Next** to move to the **Attachments** tab. Here, you can capture your current screen to send it to Microsoft. To attach additional screenshots or other files, choose **Attach Additional Files**.
+    You can even crop the screenshot directly in the browser to remove any sensitive or unrelated parts.
 
-   ![Attach a screenshot to a Visual Studio problem report](media/report-a-problem-screenshot.png)
+4. One of the best ways to help the Visual Studio engineering team solve the problem, is to provide a trace and heap dump files for them to look through. You can easily do that by recording the steps that resulted in the bug. 
 
-1. If you don't want to attach a screenshot or [record a repro](#record-a-repro), select **Next** to move to the **Summary** tab.
+    ![Record your actions](../ide/media/feedback-recording.png)
+    *Only Microsoft engineers can see the recording*
 
-1. Select **Submit** to send your report, along with any images and trace or dump files. (If the **Submit** button is grayed out, make sure that you've provided a title and description for the report.)
+5. Review the attached files and upload additional files if you believe it would help diagnose the issue.   
 
-   For information about what data is collected, see [Data we collect](developer-community-privacy.md#data-we-collect).
+    ![Attached files](../ide/media/feedback-attachments.png)
+    *Only Microsoft engineers can see the attached files*
 
-## Record a repro
+6. The last step is to hit the **Submit** button. Submitting the report will send it directly into the internal Visual Studio bug reporting system awaiting triage.
 
-Trace and heap dump files are useful in helping us diagnose problems. We appreciate it when you use the **Report a Problem** tool to record your repro steps and send the data to Microsoft. Here's how to do so:
+## When further information is needed
 
-1. After you enter a title and description for your problem, select **Next** to move to the **Attachments** tab.
+When an issue is missing important information, we assign the **Needs More Info** state. We comment on the issue with the specific information we need, and you'll receive an email notification. If we don't receive the information within seven days, then we send you a reminder. After that, we close the ticket after 14 days of inactivity.
 
-1. Select the **Record** tab.
+1. Follow the link in the email to the problem report or go to My Feedback to see all reports in the **Needs More Info** state.
 
-1. Under **Record your actions**, select the current instance of Visual Studio if you can reproduce the problem there. If you can't, for example if Visual Studio stops responding, select **\<Create a new instance>** to record the actions in a new instance of Visual Studio.
+    ![My Feedback](../ide/media/feedback-my-feedback.png)
 
-1. Select **Start Recording**. Give permission to run the tool.
+1. Selecting the Provide More Info link on the problem report navigates you to a new screen. From here, you can see what info is being requested.
 
-   ![Choose "Start Recording" to provide a trace and heap dump file in a Visual Studio problem report](../ide/media/record-dialog-box.png)
-
-1. When the **Steps Recorder** tool appears, perform the steps that reproduce the problem.
-
-1. When you're done, choose the **Stop Record** button.
-
-1. Wait a few minutes for Visual Studio to collect and package the information that you recorded.
-
-   For information about what data is collected, see [Data we collect](developer-community-privacy.md#data-we-collect).
-
-## When further information is needed (Need More Info)
-
-Starting in Visual Studio 2017 Version 15.5, there's a new workflow to help users provide additional information about problem reports.
-
-1. When a Microsoft engineer sets the [Visual Studio Developer Community](https://developercommunity.visualstudio.com/) problem to the **Need More Info** state, any user that posted, voted, followed, or commented on the problem gets a notification in the **Report A Problem** tool in Visual Studio.
-
-   ![Need More Info Notification in Visual Studio](../ide/media/nmi-notification.png)
-
-1. Click on the **View Problems** link to filter and sort the view to the problems that need attention. These problems also have an indicator next to them, to differentiate them in general search.
-
-1. Click on a problem to see the problem details view.
-
-   ![Need More Info Notification](../ide/media/nmi-details-view.png)
-
-1. To view the **Need More Info** request, click the **View their request and respond** link in the problem details view. A dialog box shows the request.
-
-   ![Need More Info Notification](../ide/media/nmi-request.png)
+   ![My Feedback](../ide/media/feedback-need-more-info.png)
 
 1. You can provide more information by adding comments, attachments, or recording steps. This experience is similar to reporting a new problem or providing additional information when voting on a problem.
 
 1. The requesting Microsoft engineer receives a notification about the extra information provided. If they have enough information to investigate, the problem state changes. Otherwise, the engineer asks for even further information.
 
-   > [!NOTE]
-   > * When you reply, the notification goes away. In its place, you see a banner that thanks you and facilitates a way to provide even more information.
-   > * Once the issue changes state, the notification goes away for everyone that's following the issue.
-   > * More than one person can reply on the same **Need More Info** request.
-   > * There isn't a **Need More Info** workflow on [Developer Community](https://developercommunity.visualstudio.com/) when you access it directly through a web browser, but you can also provide comments and attachments there.
+You can see these requests on the **My Feedback** screen along with all your other **Problems** and **Suggestions**.
 
 ## Search for solutions or provide feedback
 
 If you don't want to or can't use Visual Studio to report a problem, there's a chance the problem has already been reported and a solution posted on the [Visual Studio Developer Community](https://developercommunity.visualstudio.com/) page.
 
-If you don't have a problem to report but want to suggest a feature, there's a place for that, too. For more information, see the [Suggest a feature](https://developercommunity.visualstudio.com/content/idea/post.html?space=8) page.
+If you don't have a problem to report but want to suggest a feature, there's a place for doing that too. For more information, see the [Suggest a feature](https://developercommunity.visualstudio.com/content/idea/post.html?space=8) page.
 
 ## See also
 
+* [Developer Community Guidelines](https://docs.microsoft.com/visualstudio/ide/developer-community-guidelines)
 * [Visual Studio feedback options](../ide/feedback-options.md)
 * [Report a problem with Visual Studio for Mac](/visualstudio/mac/report-a-problem)
 * [Report a problem with C++](/cpp/how-to-report-a-problem-with-the-visual-cpp-toolset)

docs/ide/report-a-problem.md

@@ -46,7 +46,7 @@ After you report a problem, states indicate where your submissions are in their
 
 ![Need More Info state for problem reporting on Developer Community](../ide/media/ProblemStates/NeedMoreInfo.jpg)
 
-**Need More Info** indicates that we need more diagnostic information from you so that we can go forward with the investigation.  [Learn how to respond to Need More Info requests.](./how-to-report-a-problem-with-visual-studio.md#when-further-information-is-needed-need-more-info)
+**Need More Info** indicates that we need more diagnostic information from you so that we can go forward with the investigation.  [Learn how to respond to Need More Info requests.](./how-to-report-a-problem-with-visual-studio.md#when-further-information-is-needed)
 
 - - -
 

docs/install/visual-studio-build-numbers-and-release-dates.md

@@ -5,7 +5,7 @@ description: A list of released versions and build numbers for Visual Studio, so
 author: ornellaalt
 ms.author: ornella
 manager: jillfra
-ms.date: 08/11/2020
+ms.date: 08/18/2020
 ms.topic: reference
 ms.workload:
 - multiple
@@ -23,6 +23,7 @@ The following table lists the build numbers and release dates for Visual Studio
 
 | **Version**| **Channel** | **Release date** | **Build version** |
 | ---------------------- | ----------- | ---------------- | ----------------- |
+| 16.7.2 | Release | August 18, 2020 | 16.7.30413.136 |
 | 16.7.1 | Release | August 11, 2020 | 16.7.30406.217 |
 | 16.4.12 | Release | August 11, 2020 | 16.4.30406.169 |
 | 16.0.17 | Release | August 11, 2020 | 16.0.28803.806 |