Dear LibreOffice folks,
Thank you for your replies.
On 08/05/17 00:34, Thorsten Behrens wrote:
Christian Lohmaier wrote:
On Tue, Jul 25, 2017 at 12:59 PM, Paul Menzel <pmenzel@molgen.mpg.de> wrote:
So does it take over a week to get the archives published, or does
the directory need to be manually created on the server, and was
just forgotten?
Sources are made available on the mirrors the same moment when the
binaries are.
One of the reasons: it's extremely rare, but it happens at times that
full release builds on one platform show errors, or subsequent
smoketesting shows errors. In that case, a hotfix tag is pushed.
So a release is only really done, once both tag and binaries are
ready.
It’d be awesome, if we could take 5.4.1.1 as an example.
The tag was added over a week ago on August 11th.
```
commit a5be49f0c45fe24a575c7f41559aa8fc79a781a2 (tag: libreoffice-5.4.1.1)
Author: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com>
Date: Fri Aug 11 20:16:14 2017 +0200
Version 5.4.1.1, tag libreoffice-5.4.1.1
```
But even now it’s not available.
```
$ curl -I https://download.documentfoundation.org/libreoffice/src/5.4.1/
HTTP/1.1 404 Not Found
Date: Tue, 22 Aug 2017 13:32:58 GMT
Server: Apache
X-Prefix: 141.14.0.0/16
X-AS: 680
Content-Type: text/html; charset=iso-8859-1
```
It’s available as a pre-release [1]. So I am wondering, what is holding
this up? Surely, doing the release doesn’t take more than a few days.
How can I find out the reason?
Kind regards,
Paul
[1] http://dev-builds.libreoffice.org/pre-releases/src/
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.