Hi Petr,
Is there a constant rule for checking the exact version from UI directly? For
example,
Help->About
LibreOffice 3.4 340m1(Build:103)
At the moment, it looks the Build:103 means 3.4.1 RC 3. Does it reliable
enough?
Thanks for help!
Best wishes,
Yifan
On Sat, Jul 16, 2011 at 06:38:45PM +0200, gibi wrote:
Hello testers fellows,
on litmus (for example here:
https://tcm.documentfoundation.org/run_tests.cgi?test_run_id=16)
The help on "More information about how to determine the build ID How do I
determine the build ID? " contains:
<buildIDHelpText>
To determine the LibreOffice build ID, go to Help ? About LibreOffice, and
look at the "tag" line.
For example, |tag libreoffice-3.3.1.2| means that |libreoffice-3.3.1.2| is
your build ID.
</buildIDHelpText>
There is no more "tag" line in any of the 3.4 versionrc files ... at least
in linux-64 (I didn't check for Windows)
Ok, I guess that the 3.4.2rc1 should be "libreoffice-3.4.2.1" but where
could we find the new build ID we should use to report in Litmus?
It would be nice if a litmus admin could update the <buildIDHelpText> for
the 3.4 branch.
Thanks a lot!
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
--
Yifan Jiang
Libreoffice
Contact: yifan - irc.freenode.net/libreoffice
=============================================
http://www.libreoffice.org/
http://www.documentfoundation.org/
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.