Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openoffice.apache.org
MIME-Version: 1.0
In-Reply-To: <51B70E3D.7010507@googlemail.com>
References: 
 <CAK2iWdQYmRR2=KEkc2zrchPpFDKF2QV8ZyKCY3qvAJP8pK+FQA@mail.gmail.com>
	<CAK2iWdRDbi-oF-Fv_88ed=qHPAB64c3hzgjM+YD5KOQ6eMEhDA@mail.gmail.com>
	<51AEFF61.8060402@googlemail.com>
	<CAK2iWdTh8Rj5Po1hy3yWY8=MPVNmWuYW81KsgOebxVm2QppqNw@mail.gmail.com>
	<CAP-ksojUA1f7wAQngf=BkG_e2UmDc+i=MhCrnb1qBrFypMWC8Q@mail.gmail.com>
	<CAK2iWdSr8-SaQqN2nbip9-NyVYmVpjzTHhxdi0goQDc-W67rWA@mail.gmail.com>
	<CAP-ksogxNhu2s1c64ifuu3aGn0Y4BfAjLk+16-A+UfsD=gFocQ@mail.gmail.com>
	<CAK2iWdTQ4YV9xp3q5g68_MHBdiOCiBCKyZPe=XNaWGJeMvwf7Q@mail.gmail.com>
	<CAGj3216YPGbaUWeeg6Y=qXAj_GUBskyh8tLDQP0xVnbCdyxsWg@mail.gmail.com>
	<DF742033-F7F4-4879-936D-1E324326878C@apache.org>
	<CAK2iWdREOQWFjH-saqdPF9_Th0gYvyKJ--zQPV0BLb0Gn_09TQ@mail.gmail.com>
	<CAGj3214cNBOi7H2Lv8D40Rr30ajw294jdRNu-kfEa1NZ7tC7xw@mail.gmail.com>
	<CAK2iWdTQoTeg8LpM_SA8L5rUEgWGeenq82iPgX+dqpy4x3XF5g@mail.gmail.com>
	<51B7052C.6040203@googlemail.com>
	<CAP-ksojNs87ZqhFPqDQNWxKjsz6hr0ugpqNHRp2fgfxNGPtP8w@mail.gmail.com>
	<51B70E3D.7010507@googlemail.com>
Date: Tue, 11 Jun 2013 18:21:31 +0200
Message-ID: 
 <CAK2iWdQN78QVqiH06WOJnXuVcEvC6DVv5GAid3vBAQ2O19_mHA@mail.gmail.com>
Subject: Re: updates.openoffice.org
From: janI <jani@apache.org>
To: dev@openoffice.apache.org
Content-Type: multipart/alternative; boundary=001a11c2672a3ce35f04dee34a21

--001a11c2672a3ce35f04dee34a21
Content-Type: text/plain; charset=ISO-8859-1

Hi

I have now filed an issue:

https://issues.apache.org/jira/browse/INFRA-6378

I will follow up on it (actually already done on #asfinfra)

Good news is that the cert was just reported to be in our hands. It still
needs to be deployed and work with our setup.

rgds
jan I.


On 11 June 2013 13:47, Oliver-Rainer Wittmann <orwittmann@googlemail.com>wrote:

> Hi,
>
>
> On 11.06.2013 13:29, Rob Weir wrote:
>
>> On Tue, Jun 11, 2013 at 7:08 AM, Oliver-Rainer Wittmann
>> <orwittmann@googlemail.com> wrote:
>>
>>> Hi,
>>>
>>> On 11.06.2013 12:55, janI wrote:
>>>
>>>>
>>>> On 6 June 2013 18:33, Kay Schenk <kay.schenk@gmail.com> wrote:
>>>>
>>>> [snip]
>>>>
>>>>
>>>>
>>>> It seems I was too fast (or more correctly too slow), at least the
>>>> agrement
>>>> disapeared, and I have been asked to file a jira, for this part of the
>>>> https upgrade, and specifically not for the cert part (which is the
>>>> overall
>>>> task, covering both this and other issues).
>>>>
>>>> if we do it now with http, I can foresee the same thing happening with
>>>> the
>>>> https transfer, so I will highly recommend (as discussed earlier) that
>>>> we
>>>> forget updates for 4.0 and do it for 4.1 when the cert is installed.
>>>>
>>>> Of course if the community, want me to file a jira, and try to get it
>>>> done
>>>> for 4.0, I will do it.
>>>>
>>>> The cert is delayed, because of no response from the sponsor. There is
>>>> at
>>>> the moment a request to buy it instead. There are no jira detailing this
>>>> issue, just some irc communication.
>>>>
>>>>
>>> Thanks for your work and eye-keeping on it.
>>>
>>> Thus, we will not have a cert for openoffice.org in time for the AOO 4.0
>>> release.
>>>
>>> Can we go for the _corrected_ fallback URL
>>> https://ooo-updates.apache.org
>>> for AOO 4.0 or do we have to keep https://ooo-site.apache.org?
>>>
>>> Both would be fine for me, but I heard that https://ooo-site.apache.orgwill
>>> not work for ever.
>>>
>>>
>>
>> Let's get a JIRA issue entered for creating that subdomain.  I think
>> Daniel suggested it that subdomain originally.  That gives us the
>> required SSL support for 4.0.
>>
>>
> +1
>
>
> Best regards, Oliver.
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.org<dev-unsubscribe@openoffice.apache.org>
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>

--001a11c2672a3ce35f04dee34a21--