Bug 1597 - Enh: Greater clarity over status of versions needed.

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug 1597 - Enh: Greater clarity over status of versions needed.

Gale
Administrator
In resolving this Enh: I want to go on record with my minority view
that this does not go quite far enough for non-alpha builds in
directly identifying whether the build is the final release in About
Audacity and Welcome Screen.

2.1.3 proved that even RC's can be dangerous. When ALPHA=0 I think the
AUDACITY_VERSION_STRING (while still saying "Audacity 2.2.0" or
whatever version) could operate as a "Check online" link,  and that
"Id <commit hash>" could be to right of the version string in standard
or slightly smaller font, with the commit hash link going to GitHub as
now.

This makes it much quicker for support workers to identify or request the Id
information. and more likely that users of an RC will find that out
for themselves not too long after release.

Of course I appreciate there may be resistance to changing the simple
message of the "version string on its own", so I have not reopened the
Enh:. I might still reopen it if users complain about the now fixed
data loss problems in what they think is the finished 2.1.3.

I do agree we don't want to rebuild to turn the approved RC into a release.


Gale

------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|

Re: Bug 1597 - Enh: Greater clarity over status of versions needed.

James Crook
+1 on going further with this than what we currently have after 2.1.3.

I knew this was likely with an enhancement for RC3 - that exactly what
the feature is would still be in flux, but thought it worth doing the
first step anyway.

Other things to also think about:
- Can't currently cut and paste from the html about-box text.
- The script on audacityteam.org can be tweaked.  For example it could
show the CommitID and timestamp since they are passed in to it.  Useful
if users are asked to cut and paste what they see on the
check-for-updates link.
- Version number of Audacity is not on the Build information page.  
Shouldn't it be?  [i.e. Collect related information together]
- Audacity Log could show commit-ID and build timestamp, rather than
just the version number.
- The first link in the about box could be
http://www.audacityteam.org/?version rather than just
http://www.audacityteam.org/.
- The Commit ID and the GitHub information it links to won't mean
anything to 99% of users.


---James.



On 3/11/2017 2:09 AM, Gale Andrews wrote:

> In resolving this Enh: I want to go on record with my minority view
> that this does not go quite far enough for non-alpha builds in
> directly identifying whether the build is the final release in About
> Audacity and Welcome Screen.
>
> 2.1.3 proved that even RC's can be dangerous. When ALPHA=0 I think the
> AUDACITY_VERSION_STRING (while still saying "Audacity 2.2.0" or
> whatever version) could operate as a "Check online" link,  and that
> "Id <commit hash>" could be to right of the version string in standard
> or slightly smaller font, with the commit hash link going to GitHub as
> now.
>
> This makes it much quicker for support workers to identify or request the Id
> information. and more likely that users of an RC will find that out
> for themselves not too long after release.
>
> Of course I appreciate there may be resistance to changing the simple
> message of the "version string on its own", so I have not reopened the
> Enh:. I might still reopen it if users complain about the now fixed
> data loss problems in what they think is the finished 2.1.3.
>
> I do agree we don't want to rebuild to turn the approved RC into a release.
>
>
> Gale


------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|

Re: Bug 1597 - Enh: Greater clarity over status of versions needed.

Gale
Administrator
Thanks, James.

Further tweaks would be nice but probably only P5/P6 for alpha
testers.

I think the main reason to reopen is easy identification of the approved
alpha=0 as really being the finished release. Perhaps that should be a
new Enh and focus on that? If tweaks benefit alpha users too, all the
better.


On 11 March 2017 at 11:26, James Crook <[hidden email]> wrote:
> +1 on going further with this than what we currently have after 2.1.3.
>
> I knew this was likely with an enhancement for RC3 - that exactly what
> the feature is would still be in flux, but thought it worth doing the
> first step anyway.
>
> Other things to also think about:
> - Can't currently cut and paste from the html about-box text.

Would be nice for other reasons too, but OS copy works, at least
on Windows.


> - The script on audacityteam.org can be tweaked.  For example it could
> show the CommitID and timestamp since they are passed in to it.  Useful
> if users are asked to cut and paste what they see on the
> check-for-updates link.

Show where? We have timestamp now in the browser address bar
if user clicks a "Check*" link in the app.


> - Version number of Audacity is not on the Build information page.
> Shouldn't it be?  [i.e. Collect related information together]

I don't think it matters that much given normal users won't look
there and given About Audacity never opens on that tab.


> - Audacity Log could show commit-ID and build timestamp, rather than
> just the version number.

+1.


> - The first link in the about box could be
> http://www.audacityteam.org/?version rather than just
> http://www.audacityteam.org/.

Do you mean http://www.audacityteam.org/download/?from_ver=...?

I think it would be cleaner if the link stayed at http://www.audacityteam.org/.

I do think that for ALPHA=0, "Audacity x.x.x" in Welcome Screen and
About Audacity should be a link and act the same as the "Check*" links,
giving the custom text above the download page. Why? Because
"Audacity x.x.x" can mean any RC or the finished release - it has only
that generalised meaning.


> - The Commit ID and the GitHub information it links to won't mean
> anything to 99% of users.

Agreed, but as I said, that information is for ease of support workers
in helping users. We have to ask for the "full three-digit version number"
of Audacity from About Audacity many times a day on the Forum.

If we suspected user had an RC, we could just ensure user quoted
the "full three-digit version number" and the id after that. However
if "Audacity x.x.x" was a version check link and the commit Id at
least was in the log, that would be a reasonable compromise for me.



Gale


> On 3/11/2017 2:09 AM, Gale Andrews wrote:
>> In resolving this Enh: I want to go on record with my minority view
>> that this does not go quite far enough for non-alpha builds in
>> directly identifying whether the build is the final release in About
>> Audacity and Welcome Screen.
>>
>> 2.1.3 proved that even RC's can be dangerous. When ALPHA=0 I think the
>> AUDACITY_VERSION_STRING (while still saying "Audacity 2.2.0" or
>> whatever version) could operate as a "Check online" link,  and that
>> "Id <commit hash>" could be to right of the version string in standard
>> or slightly smaller font, with the commit hash link going to GitHub as
>> now.
>>
>> This makes it much quicker for support workers to identify or request the Id
>> information. and more likely that users of an RC will find that out
>> for themselves not too long after release.
>>
>> Of course I appreciate there may be resistance to changing the simple
>> message of the "version string on its own", so I have not reopened the
>> Enh:. I might still reopen it if users complain about the now fixed
>> data loss problems in what they think is the finished 2.1.3.
>>
>> I do agree we don't want to rebuild to turn the approved RC into a release.
>>
>>
>> Gale
>
>
> ------------------------------------------------------------------------------
> Announcing the Oxford Dictionaries API! The API offers world-renowned
> dictionary content that is easy and intuitive to access. Sign up for an
> account today to start using our lexical data to power your apps and
> projects. Get started today and enter our developer competition.
> http://sdm.link/oxford
> _______________________________________________
> Audacity-quality mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/audacity-quality

------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|

Re: Bug 1597 - Enh: Greater clarity over status of versions needed.

James Crook
I think the feature needs more design and discussion, as there are
competing pulls.
We don't want the user to have a cluttered screen, but we do want
support people to have more information.

Some more comments are in line below.

---James.

On 3/11/2017 9:30 PM, Gale Andrews wrote:
> Thanks, James.
>
> Further tweaks would be nice but probably only P5/P6 for alpha
> testers.
>
> I think the main reason to reopen is easy identification of the approved
> alpha=0 as really being the finished release. Perhaps that should be a
> new Enh and focus on that? If tweaks benefit alpha users too, all the
> better.
User will always have to click on something somewhere to get that
confirmation.  The question is what we tell them to click on.  I'd like
it to be something like:

'Click on help->Check Version, and then cut and paste what is in the
yellow box and send it to us in your email.'

>> - The script on audacityteam.org can be tweaked.  For example it could
>> show the CommitID and timestamp since they are passed in to it.  Useful
>> if users are asked to cut and paste what they see on the
>> check-for-updates link.
> Show where? We have timestamp now in the browser address bar
> if user clicks a "Check*" link in the app.
It is easy to change the current website message to be in a yellow
information box, and to show the timestamp and Commit ID in that yellow
box too.

In the browser bar is (marginally) less convenient for the user to cut
and paste, and so makes telling them what to do harder, I was thinking.

>
>> - Version number of Audacity is not on the Build information page.
>> Shouldn't it be?  [i.e. Collect related information together]
> I don't think it matters that much given normal users won't look
> there and given About Audacity never opens on that tab.
OK.

>
>> - Audacity Log could show commit-ID and build timestamp, rather than
>> just the version number.
> +1.
>
>
>> - The first link in the about box could be
>> http://www.audacityteam.org/?version rather than just
>> http://www.audacityteam.org/.
> Do you mean http://www.audacityteam.org/download/?from_ver=...?
I don't want to display the full version checking string as it is rather
long, but do want to pass it to the script.  Using '...' to indicate
that is probably a better solution than mine.

> I think it would be cleaner if the link stayed at http://www.audacityteam.org/.
>
> I do think that for ALPHA=0, "Audacity x.x.x" in Welcome Screen and
> About Audacity should be a link and act the same as the "Check*" links,
> giving the custom text above the download page. Why? Because
> "Audacity x.x.x" can mean any RC or the finished release - it has only
> that generalised meaning.
Has +'s and -'s.  I don't think a hyperlink on big text looks good. It's
relatively unusual.  We also already seem to me to have more hyperlinks
than we really need in the paragraphs above 'credits' - maybe more text
than we need too, given that we link to the audacityteam.org welcome page.

>
>> - The Commit ID and the GitHub information it links to won't mean
>> anything to 99% of users.
> Agreed, but as I said, that information is for ease of support workers
> in helping users. We have to ask for the "full three-digit version number"
> of Audacity from About Audacity many times a day on the Forum.
>
> If we suspected user had an RC, we could just ensure user quoted
> the "full three-digit version number" and the id after that. However
> if "Audacity x.x.x" was a version check link and the commit Id at
> least was in the log, that would be a reasonable compromise for me.

In case you are not aware of what the script could be adjusted to do:

Actual release could say '2.1.3 Current Release - Congrats you're using
the latest Release' on the version check page.
Release candidates can say e.g. '(Deprecated) 2.1.3 Release Candidate
RC1'.  on the version check page.
Unknown versions can say e.g. 'Unknown Version of Audacity 2.1.3
CommitID: afc451 Time: Mar8201714:01:58'

--James.

------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|

Re: Bug 1597 - Enh: Greater clarity over status of versions needed.

Gale
Administrator
On 11 March 2017 at 22:24, James Crook <[hidden email]> wrote:

> I think the feature needs more design and discussion, as there are
> competing pulls.
> We don't want the user to have a cluttered screen, but we do want
> support people to have more information.
>
> Some more comments are in line below.
>
> ---James.
>
> On 3/11/2017 9:30 PM, Gale Andrews wrote:
>> Thanks, James.
>>
>> Further tweaks would be nice but probably only P5/P6 for alpha
>> testers.
>>
>> I think the main reason to reopen is easy identification of the approved
>> alpha=0 as really being the finished release. Perhaps that should be a
>> new Enh and focus on that? If tweaks benefit alpha users too, all the
>> better.
> User will always have to click on something somewhere to get that
> confirmation.  The question is what we tell them to click on.  I'd like
> it to be something like:
>
> 'Click on help->Check Version, and then cut and paste what is in the
> yellow box and send it to us in your email.'
>
>>> - The script on audacityteam.org can be tweaked.  For example it could
>>> show the CommitID and timestamp since they are passed in to it.  Useful
>>> if users are asked to cut and paste what they see on the
>>> check-for-updates link.
>> Show where? We have timestamp now in the browser address bar
>> if user clicks a "Check*" link in the app.
> It is easy to change the current website message to be in a yellow
> information box, and to show the timestamp and Commit ID in that yellow
> box too.
>
> In the browser bar is (marginally) less convenient for the user to cut
> and paste, and so makes telling them what to do harder, I was thinking.
>
>>
>>> - Version number of Audacity is not on the Build information page.
>>> Shouldn't it be?  [i.e. Collect related information together]
>> I don't think it matters that much given normal users won't look
>> there and given About Audacity never opens on that tab.
> OK.
>>
>>> - Audacity Log could show commit-ID and build timestamp, rather than
>>> just the version number.
>> +1.
>>
>>
>>> - The first link in the about box could be
>>> http://www.audacityteam.org/?version rather than just
>>> http://www.audacityteam.org/.
>> Do you mean http://www.audacityteam.org/download/?from_ver=...?
> I don't want to display the full version checking string as it is rather
> long, but do want to pass it to the script.  Using '...' to indicate
> that is probably a better solution than mine.
>
>> I think it would be cleaner if the link stayed at http://www.audacityteam.org/.
>>
>> I do think that for ALPHA=0, "Audacity x.x.x" in Welcome Screen and
>> About Audacity should be a link and act the same as the "Check*" links,
>> giving the custom text above the download page. Why? Because
>> "Audacity x.x.x" can mean any RC or the finished release - it has only
>> that generalised meaning.
> Has +'s and -'s.  I don't think a hyperlink on big text looks good. It's
> relatively unusual.  We also already seem to me to have more hyperlinks
> than we really need in the paragraphs above 'credits' - maybe more text
> than we need too, given that we link to the audacityteam.org welcome page.

The "Welcome Screen" is the main "problem". It has no link to check
what non-alpha version you have. Alpha builds have such a link in the
Welcome Screen.

"Audacity.x.x.x" is not a long string. I think some link could be provided
to right of it in smaller font. I thought it was neatest just to show commit
ID as the link text.

Or of course put the link somewhere else in the Help text in that screen.


>>> - The Commit ID and the GitHub information it links to won't mean
>>> anything to 99% of users.
>> Agreed, but as I said, that information is for ease of support workers
>> in helping users. We have to ask for the "full three-digit version number"
>> of Audacity from About Audacity many times a day on the Forum.
>>
>> If we suspected user had an RC, we could just ensure user quoted
>> the "full three-digit version number" and the id after that. However
>> if "Audacity x.x.x" was a version check link and the commit Id at
>> least was in the log, that would be a reasonable compromise for me.
>
> In case you are not aware of what the script could be adjusted to do:
>
> Actual release could say '2.1.3 Current Release - Congrats you're using
> the latest Release' on the version check page.
> Release candidates can say e.g. '(Deprecated) 2.1.3 Release Candidate
> RC1'.  on the version check page.
> Unknown versions can say e.g. 'Unknown Version of Audacity 2.1.3
> CommitID: afc451 Time: Mar8201714:01:58'

I know the script can be tailored, but from the Welcome Screen and
first tab of About Audacity there is currently no way to call the script.


Gale

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|

Re: Bug 1597 - Enh: Greater clarity over status of versions needed.

James Crook
On 3/13/2017 7:34 PM, Gale Andrews wrote:
> The "Welcome Screen" is the main "problem". It has no link to check
> what non-alpha version you have. Alpha builds have such a link in the
> Welcome Screen.
>
> "Audacity.x.x.x" is not a long string. I think some link could be provided
> to right of it in smaller font. I thought it was neatest just to show commit
> ID as the link text.
>
> Or of course put the link somewhere else in the Help text in that screen.

Elsewhere the commit id links to the github commit.
So I think check online (as a link) below "Audacity x.x.x" is better.

OR in welcome and About we have

Audacity 2.1.3 ffe4aa

With ffe4aa is in a smaller font and as a hyperlink to the download
page, and the download page has an additional link to the github commit.
Possibly we remove check online from the Build Information page, since
users can do it anyway from the welcome, the about page and the
help->check-for-updates link, and the number of ways to get there seems
OTT to me.

Anyway, to be decided during 2.2.0

--James.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality