When I unpack the final relase rpm's ".tar.gz" files, the filefolders created still say: LibO_3.3.0rc4_Linux_x86-64_install-rpm_en-US LibO_3.3.0rc4_Linux_x86-64_helppack-rpm_en-US LibO_3.3.0rc4_Linux_x86-64_helppack-rpm_fr LibO_3.3.0rc4_Linux_x86-64_langpack-rpm_fr Should the file folders still say "rc4" or should they not just be eliminated. People will think that these are still RC4 and question whether or not these are final versions. The same should be applied on all platforms Win, Mac, Linux. Great work on the final version! Looks and feels great! Cheers Marc
this is because the final is a *exact* copy of rc4. See the release notes: "This release is bit-for-bit identical to the Release Candidate 4, so you don't need to download or reinstall if you have that version already."
(In reply to comment #1) > this is because the final is a *exact* copy of rc4. See the release notes: > > "This release is bit-for-bit identical to the Release Candidate 4, so you don't > need to download or reinstall if you have that version already." Thanks for your info. Sorry, maybe I am not well informed about these steps. But, if a final version of software is attained, would it not make sense to drop the "RCXXXX" tag? Or maybe I just have never noticed the "RCXXXX" on any other final version of software? Is this standard procedure in the numbering scheme? I would think that the "final" designation would remove all tags. We went trough "alpha", "beta", "rc" and the final step is final. Just wondering. Thanks for any other info. on this.
Please note that we expect an overwhelming majority of users on Linux to use their distro's packaging of LibreOffice, once the distros pick it up and release it through their normal channels. The distros presumably will have no reason to include the string "rc4" in any way or form in their package names of LO 3.3. This is just a "problem" for people using our generic binaries.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.