>* use stat() on the file to get a meaningful date and display that (more
>meaningful to an end-user)
Would that show the date the update was applied, or the actual release date of
the last upgrade? Also, this may not provide a meaningful reference point if
we can't use the same information regarding the target build that the upgrade
will leave you in. In the latter case, currently *all* we know is the build
number.
>* include build id between parenthesis, but split it to be less confusing
>
>So instead of:
>20130800
>show:
>2013/08/01 13:34 (201308.00)
I do like putting the build number in parentheses. Many OSes/applications do
this with even more cryptic build numbers than ours. ;)
On Aug 02, 2013, at 02:54 PM, Loïc Minier wrote:
>* use stat() on the file to get a meaningful date and display that (more
>meaningful to an end-user)
Would that show the date the update was applied, or the actual release date of
the last upgrade? Also, this may not provide a meaningful reference point if
we can't use the same information regarding the target build that the upgrade
will leave you in. In the latter case, currently *all* we know is the build
number.
>* include build id between parenthesis, but split it to be less confusing
>
>So instead of:
>20130800
>show:
>2013/08/01 13:34 (201308.00)
I do like putting the build number in parentheses. Many OSes/applications do
this with even more cryptic build numbers than ours. ;)