preparing release

GoogleTestAdapter/VsPackage/ReleaseNotes/History.cs

@@ -28,7 +28,7 @@ static History()
                 { new Version(0, 4, 0, 1), new DateTime(2016, 3, 15) },
                 { new Version(0, 5, 0, 0), new DateTime(2016, 3, 25) },
                 { new Version(0, 5, 0, 1), new DateTime(2016, 3, 27) },
-                { new Version(0, 6, 0, 0), new DateTime(2016, 4, 20) }
+                { new Version(0, 6, 0, 0), new DateTime(2016, 5, 4) }
             };
         }
 

GoogleTestAdapter/VsPackage/Resources/ReleaseNotes/0.5.0.md

@@ -2,6 +2,4 @@
 * enhancement: new option *Test name separator* allows to replace the `/` within Google Test names (which causes VS to truncate test names if the test explorer window is not wide enough) with another string ([#23](https://github.com/csoltenborn/GoogleTestAdapter/issues/23))
 * enhancement: new option *Parse symbol information* allows to switch off parsing of the tests' .pdb files (which speeds up test discovery for the cost of having no test source locations and no macro based traits) ([#41](https://github.com/csoltenborn/GoogleTestAdapter/issues/41), thanks to [Peter Budai](https://github.com/peterbudai) for the pull request)
 * enhancement: license is now provided in a more standardized way ([#40](https://github.com/csoltenborn/GoogleTestAdapter/issues/40), thanks to [Peter Budai](https://github.com/peterbudai)) 
-* bugfix: traits information had been optimized away by certain compiler optimizations ([#39](https://github.com/csoltenborn/GoogleTestAdapter/issues/39))
-
-Note that the *Enable parallel test execution* option has been renamed to *Parallel test execution*, resulting in lost settings of that option inside VS. Solution and user file settings are not affected.
+* bugfix: traits information had been optimized away by certain compiler optimizations ([#39](https://github.com/csoltenborn/GoogleTestAdapter/issues/39))

GoogleTestAdapter/VsPackage/Resources/ReleaseNotes/0.6.0.md

@@ -1,6 +1,4 @@
 * enhancement: the location of the pdb file is now also looked up within the according test executable, providing source locations and traits even in cases were the pdb's name is different from the name of the test executable, or where the pdb ends up outside of the executable's path ([#45](https://github.com/csoltenborn/GoogleTestAdapter/pull/45), thanks to [Stefan Winkler](https://github.com/nafest) for the pull request)
 * enhancement: options are now grouped into categories ([#44](https://github.com/csoltenborn/GoogleTestAdapter/issues/44))
 * enhancement: release notes are shown after the extension has been updated ([#48](https://github.com/csoltenborn/GoogleTestAdapter/issues/48))
-* bugfix: if [Dia crashed](https://connect.microsoft.com/VisualStudio/feedback/details/1908082/dia140-fails-in-various-ways-when-using-debug-fastlink), the pdb under analysis remained locked, and the tests contained in the according test executable were not found (part of [#46](https://github.com/csoltenborn/GoogleTestAdapter/issues/46), thanks to [Jesse Olmer](https://github.com/JesseOlmer) for report and example solution)
-
-Note that the options to assign traits by means of regexes have been renamed, resulting in lost settings of these options inside VS. Solution and user file settings are not affected. Make sure you backup your existing settings before updating; in case VS has updated the extension before you had the chance to backup your settings, you can look them up by using the regedit tool: the adapter's settings are located at `HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualStudio\[12.0|14.0]\DialogPage\GoogleTestAdapter.VsPackage.OptionsPages.GeneralOptionsDialogPage`.
+* bugfix: if [Dia crashed](https://connect.microsoft.com/VisualStudio/feedback/details/1908082/dia140-fails-in-various-ways-when-using-debug-fastlink), the pdb under analysis remained locked, and the tests contained in the according test executable were not found (part of [#46](https://github.com/csoltenborn/GoogleTestAdapter/issues/46), thanks to [Jesse Olmer](https://github.com/JesseOlmer) for report and example solution)

README.md

@@ -36,7 +36,7 @@ Google Test Adapter (GTA) is a Visual Studio extension providing test discovery
 Google Test Adapter can be installed in two ways:
 
 * Install through the Visual Studio Gallery at *Tools/Extensions and Updates* - search for *Google Test Adapter*. This will make sure that the extension is updated automatically
-* Download and launch the [VSIX installer](https://github.com/csoltenborn/GoogleTestAdapter/releases/download/v0.5.1/GoogleTestAdapter-0.5.1.vsix) (which can also be downloaded from the [Visual Studio Gallery](https://visualstudiogallery.msdn.microsoft.com/94c02701-8043-4851-8458-34f137d10874))
+* Download and launch the [VSIX installer](https://github.com/csoltenborn/GoogleTestAdapter/releases/download/v0.6.0/GoogleTestAdapter-0.6.0.vsix) (which can also be downloaded from the [Visual Studio Gallery](https://visualstudiogallery.msdn.microsoft.com/94c02701-8043-4851-8458-34f137d10874))
 
 After restarting VS, your tests will be displayed in the test explorer at build completion time. If no or not all tests show up, have a look at the [trouble shooting section](#trouble_shooting).
 

appveyor.yml

@@ -1,4 +1,4 @@
-version: 0.5.1.{build}
+version: 0.6.0.{build}
 os: Visual Studio 2015
 configuration: Release
 platform: Any CPU