Currently the Windows Master builds are named e.g. master~2011-11-16_23.49.24_LibO-Dev_OOO350m1_Win_x86_install_en-US.exe After unpacking an installation folder is created, named e.g. LibO-dev 3.5 (4ec47f5f) Installation Files And opening the About box the build name is LibO-dev 3.5.0 Build ID: 4f11d0a-adcf6d5-c4bb9bd Isn't it possible that all elements have a common name? I have no idea if the code "4ec47f5f" in the installation folder is enough (or has any meaning) but it would be perfect to have master~2011-11-16_23.49.24_LibO-Dev_OOO350m1_4ec47f5f_Win_x86_install_en-US.exe LibO-dev 3.5 (4ec47f5f) Installation Files LibO-dev 3.5.0 Build ID: 4ec47f5f and maybe apply the same to other OS builds? master~2011-11-16_22.31.10_LibO-Dev_OOO350m1_4ec47f5f_Linux_x86-64_helppack-rpm_de.tar.gz master~2011-11-16_01.40.47_LibO-Dev-SDK_OOO350m1_4ec47f5f_MacOS_x86_install_en-US.dmg
I believe Naming convention for Master builds can be improved. Currently its not easy to assign the Build identifier to a source code, I frequentyl hear the question "what date", and in future "what tinderbox" might be added. Do not make the names too long, everything without information should be eliminated, may be "master~2011-11-15_17.38.22_LibO-Dev_OOO350m1_Win_x86_install_en-US_de_fr.exe" Can be reduced to "m20111115_173822_LibO-Dev_OOO350m1_Win_x86_install_en-US_de_fr_d38713d-5d03837-ca7e6f5-c4bb9bd-ce71330.exe with the additional Build identitier? And may be an abbreviation of the tinderbox name should be integrated? Only a quick idea! That's nothing where we are in a hurry.
Currently LibO not uses exe files for installs and not extracts installer to folder. May be problems is fixed? Problem was this: > After unpacking an installation folder is created, named e.g. > LibO-dev 3.5 (4ec47f5f) Installation Files and impossible was to understand, what for folder it is
@sasha: Currenly .msi files are used?!
Releases and candidates are msi. Master not tested, but here I see msi: http://dev-builds.libreoffice.org/daily/Win-x86@15-Prague_Win32/libreoffice-3-5/2012-04-20_21.51.25/
@sasha, all installers are now msi (except for the 3.4.x branch which is no longer developed) The problem with the installation folder is indeed solved :) The point here is that the name of the msi file still doesn't help in determining which master build is installed. Example master~2012-04-13_22.07.42_LibO-Dev_3.6.0alpha0_Win_x86_install_en-US.msi installs version 3.6.0alpha0+ (Build ID: e00e693) These two pieces of information don't match and don't help at all. If I wanted someone to test the same build it would be much more helpful to indicate the path to the info file than any of the above http://dev-builds.libreoffice.org/daily/Win-x86@6-fast/master/2012-04-13_22.07.42/master~2012-04-13_22.07.42_build_info.txt
So, what information should be added to filename?
I agree, sometimes it's difficult to compare results without precise pull time information (what you find in the file name and for master and daliy builds in the additional text file in the download folder). Currently I have a list where I collect all info th the various builds I have, but that's annoying, it would be fine to have that in Help / About. But we should not overwhelm normal users with such expert information, so I still believe we should have a "details" button in the dialog 8or something similar) leading to such information. @Petr: any Idea how to get that info with acceptable costs and in an appropriate way into the dialog?
One possibility would be to show this information only in dev builds that are used for the daily builds but not for official BETAs/RCs/releases. Another possibility would be to add this information to the string printed by "libreoffice --version".
(In reply to comment #8) > One possibility would be to show this information only in dev builds I would prefer to have it in any build, otherwise in the Branch daily builds it might be a problem to find out whether the used build is younger or older that a particular release. > Another possibility would be to add this information to the string printed by > "libreoffice --version". Sounds like a command line thingy? We WIN users hate that. If my assumption is correct, it's not easy to get that info. I have lots of links to lots of server installations of builds, and when I want to get that info, I would have to check the path where the .exe are, cmd, go to path, run command, brrrrr. And sometimes I have several builds running simultaneously for comparison, currently I have to copy the Build IDs and search a hand made listing for that ID; in the list I also have the pull time / date. Not a big problem, but irksome. I prefer info in the dialog.
This feature has been added to the 4.1 branch Example: File name master~2013-01-24_22.52.49_LibO-Dev_4.1.0.0.alpha0_Win_x86.msi About box information Version 4.1.0.0.alpha0+ (Build ID: 2823789bec0c029d9714aff0ed65923e23177ef) TinderBox: Win-x86@6, Branch:master, Time: 2013-01-24_22:52:49 Thank you Petr ;)
Works perfect, saves 1,5 hours/a for me :-)