Bugzilla – Bug 1597
Enh: Greater clarity over status of versions needed.
Last modified: 2018-08-20 11:45:58 UTC
For efficient progression from RC to release, we would like to release the exact same assembly that we tested as an RC. The enhancement proposal is that when doing check-versions, Audacity also passes more information, such as the commitID, the compile date and perhaps checksum of exe. With this information, a dynamic information page at audacityteam.org can give version specific information, e.g: This is an Alpha with a serious data loss bug, do not use. This is a release version, but there is a more up to date version now. This is an experimental build that has had two months of concerted use, and seems to be stable.
For ALPHA builds I'm suggesting that in release versions we run check version automatically at start up.
DEVEL-FIXMADE https://github.com/audacity/audacity/commit/c53e2dbb778c04a992a58c2d8a81ade5ed465764 Gale - This still needs the dynamic script on our webserver to give you some information about the build, based on the extra information now passed to it. So don't CLOSE until that is in place too. This opens our update-check web page for an alpha build (if welcome screen is not suppressed).
I've now added the scriptlet to our website, on a test page. Once we are happy with it, it can be on the download page too. http://wiki.audacityteam.org/wiki/Version_Checking_Scriptlet
Testing on W10 audacity-win-rfacaeb9-2.1.3-alpha-27-feb-17 Running this alpha version puts up the Website page (in Microsoft Edge) with the warning. a) The warng page appeasrs full screen, no problem with that, but imeediately after it flashes up it is overlaid by the Audacity Window and welcome mat dialog thus obscuring the information we are trying to show to the user. b) I don't think the text is right or good either when it says: "Get a Better Version of Audacity" the released version that it steers you to is not necessarily "better" at all. What it is is a released production version which is fully supported. I feel we could make that clearer. Stressing the lack of support should be sufficiently off-putting for whom alpha testing is inappropriate.
I don't get the Microft edge splash screen warning when I try to run 2.1.0 or 2.1.1 ( or 1.3.14 or 1.2.6) - should I expect to?
Testing on Macbook Pro Sierra 10.12.3 with 27Feb17 alpha facaeb9 On Mac the Audacity window apperas first and is the oveerlaid with the Safari window with the warning message clearly displayed
Thanks for testing and feedback. I've changed things so that the splash screen no longer invokes the browser, but the check version and check online link still do. Alphas now have additional text, based mostly on text Peter suggested, actually in the Welcome message. https://github.com/audacity/audacity/commit/fc42fd9b0d1f051d7f6d05d2b1e5242fdcfbc55e
Testing on W10 and Sierra 10.12.3 01Apr17 rfc42fd9 Both platforms now display the alpha warning as the entry mat with the abilty for the user to choose to drill for further information on the Audacity website. Wording looks much better.
Seems to be working as intended, on Linux too. In resolving it I stand by my reservations that this improvement does not go quite far enough for release builds, as stated again on -quality.
