Bug 53347 - TDF Site: Download 3.5.6RC2 in same folder as 3.6.0
Summary: TDF Site: Download 3.5.6RC2 in same folder as 3.6.0
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: WWW (show other bugs)
Version: 3.5.6.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
QA Contact:
URL: http://dev-builds.libreoffice.org/pre...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-10 15:05 UTC by Rainer Bielefeld Retired
Modified: 2012-08-28 15:50 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Rainer Bielefeld Retired 2012-08-10 15:05:00 UTC
Under a.m. URL I found WIN 3.5.6.2 together with LibO_3.6.0_Win_x86_install_multi.msi and 3.6.0 help.

I think those different versions should be in different folders (of course, I downloaded 3.6.0 together with 3.5 help files ...)

And what a strange 3.6.0 installer is that far away from all our name conventions?

This hodge podge seems to be WIN only.
Comment 1 Christian Lohmaier 2012-08-28 15:50:46 UTC
Not a bug/worksforme.

The pre-release page is not for the general public, but for those who want to try out the build before it is distributed over the mirror network.

And as LO usually maintains two versions at a time, it is used for both.

i.e. if 3.5.x as well as 3.6.x will end up in there before being distributed to the mirrors.

However it is unusual to release two versions at the same time, so it is unlikely that there will be a confusion about the builds there.

But people tend to make mistakes, and sometimes forget to delete the old stuff before putting the new stuff out :-)

That the 3.6.0 ones were still on there was a mistake, they should have been removed after the build was available using the regular mirrors.

(It was windows-only, since windows builds were replaced just after the release, since the digital signature was missing)


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.