From ea14a117dfb9d421c91d0ca7c2f7f604f32ebbfc Mon Sep 17 00:00:00 2001
From: Paul Licameli <paul.licameli@audacityteam.org>
Date: Wed, 23 Aug 2017 11:45:33 -0400
Subject: [PATCH] Expose the benchmark tool in end-user builds

---
 src/Menus.cpp | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/src/Menus.cpp b/src/Menus.cpp
index 4bbbfdf2b..38fd36169 100644
--- a/src/Menus.cpp
+++ b/src/Menus.cpp
@@ -1203,12 +1203,15 @@ void AudacityProject::CreateMenusAndCommands()
       c->BeginSubMenu( _("&Tools") );
       c->AddItem(wxT("Screenshot"), _("&Screenshot Tools..."), FN(OnScreenshot));
 
-#if IS_ALPHA
+// PRL: team consensus for 2.2.0 was, we let end users have this diagnostic,
+// as they used to in 1.3.x
+//#if IS_ALPHA
       // TODO: What should we do here?  Make benchmark a plug-in?
       // Easy enough to do.  We'd call it mod-self-test.
 
       c->AddItem(wxT("Benchmark"), _("&Run Benchmark..."), FN(OnBenchmark));
-#endif
+//#endif
+
       c->EndSubMenu();
       c->AddSeparator();