Apache OpenOffice (AOO) Bugzilla – Issue 20175
Displaying build/RC version information in Help / about
Last modified: 2013-08-07 15:35:09 UTC
Help; About OpenOffice.org, should give full version information. So, with rc5 that I am currently running it should say: OpenOffice.org 1.1.0 rc5. Reason: Makes it clear which version you are running for reporting bugs. This is otherwise not easy to track if, like use as a school, we have loads of machines trialling OOo. ('Which version is that? RC4 or RC5?' 'Don't know, I didn't do the last upgrade on this machine?')
I agree; Help / About should show the build number. It would be helpful.
FPE: About box *does* show the build number if you enter Ctrl+S-D-T in the about box. Look for "build number" in the help index.
.
Using CTRL + SDT to determine the build and version number is neither intuitive nor well known. How to get this information is an FAQ which could be avoided by simply putting it in Help > About without the extra required step. Also, using CTRL + SDT does not always provide the version -- as in the case of 1.1rc5, which provides only the build number. The version number is more useful and understandable to the average user. While I can't speak for Mark, I understood this to be the purpose of the RFE -- to eliminate the need for CTRL + SDT.
>Using CTRL + SDT to determine the build and version number >is neither intuitive nor well known. How to get this information is It's well documente in the help. >an FAQ which could be avoided by simply putting it in Help > About >without the extra required step. The standard user will not be interested in this information so adding an extra step to get it is a valid procedure. Re displaying the milestone release (Beta, RC1, 2, 3...): duplicate. *** This issue has been marked as a duplicate of 20030 ***
>The standard user will not be interested in this I am not so sure about this- esp. in situations where giving remote help (via the internet for example). Having the information in a location where many users expect to see it will simplify assisting users and giving users a better user experiance.
I don't want to get too deep into a discussion here. I'd just suggest to merge the two bugs because they are adressing the same issue -- readily identifying the version.
Agreed that the issue is documented in the help. But it would be much simpler to have it visibly there without having to consult the help. KISS
Reopen as discussed at dev@qa and users@ooo (as this is not an duplicate). Changed summary to show the difference.
Hi Frank, can you pass this on to the proper people?
Not a documentation issue.
reassign to 'tools'-team
Using PavelJ's m103 build #2 on Linux, i can see via Help -> About that there already is code available for this (Build 2, $build_date). Could this extra information also be included in _stable_ builds and release candidates, where no easy identification such as m1xx is possible?
set to wontfix. a final version is created through a simple copy of rc, so it makes no sense to require recompilation to get buid identification in. the same applies for the additional string set by --with-build-version. we need to think about another build identification which doesn't require recompilation of the office.
close issue.