[Libreoffice-qa] How long before a released build is notified by Update?

Robinson Tryon bishop.robinson at gmail.com
Tue Nov 26 10:45:49 PST 2013

On Tue, Nov 26, 2013 at 7:24 AM, Pedro <pedlino at gmail.com> wrote:
> Robinson Tryon wrote
>>> Version:
>>> Build ID: 1b3956717a60d6ac35b133d7b0a0f5eb55e9155
>> The Updater only knows about the following builds:
>>     '43286d64e6126b0915ae60d89d3177018fe63b9' => '', # rc1
>> (buildfix1)
>>     'a7d538950185d02a6b950cd1cb2dfd79435f6e2' => '', # rc1
>> (buildfix2, o\nly Windows)
> I'm confused here... How many official TDF RC1 builds are there?
> One per OS?

I'm not sure of the story here -- perhaps we had to push some special
buildfix just for Windows?
(Doing a quick scan, I see the following OS-specific builds:
OSX-only build for 3.5.0
4.0.0 RC2 for Windows
4.0.0 RC3 Final for OSX for Win Win Win ("hotfixes")

> Robinson Tryon wrote
>>> Version is also the official RC1 from TDF
>> Build ID for that one?
> Version (Build ID: 9418c72)

Here's what we have listed for 3.6.7 builds:

    # 3.6.7 versions
    'a61ad19-949f691-349cf55-3bea8d1-2c85eb' => '',
    'e183d5b-f8ccaf6-3804794-95b4be8-895629' => '', # Final
(last of 3.6 series)

I don't see that build in there. Cloph?

Couple of thoughts:

1) Could we further automate the build process to ensure that build
ids get uploaded?

2) Could we upload a text manifest/summary along with builds?
(e.g. look at http://downloadarchive.documentfoundation.org/libreoffice/old/
There's no quick and easy way for me to find the build-id of that
build. A text manifest with build-id, build date, and a few other
small pieces of metadata in a standardized format could be very


More information about the Libreoffice-qa mailing list