Hi,
On 11.06.2013 18:21, janI wrote:
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
On 6 June 2013 18:33, Kay Schenk kay.sch...@gmail.com wrote:
On Thu, Jun 6, 2013 at 12:54 AM, janI j...@apache.org wrote:
On 6 June 2013 04:15, Dave Fisher w...@apache.org wrote:
On Jun 5, 2013, at 12:37 PM, Kay Schenk kay.sch...@gmail.com wrote:
On Wed, Jun 5, 2013 at 8:50 AM,
Hi,
On 11.06.2013 12:55, janI wrote:
On 6 June 2013 18:33, Kay Schenk kay.sch...@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
On 6 June 2013 04:15, Dave Fisher w...@apache.org wrote:
On Jun 5, 2013, at 12:37 PM, Kay Schenk kay.sch...@gmail.com wrote:
On Wed, Jun 5, 2013 at 8:50 AM, janI j...@apache.org wrote:
On 5 June 2013 17:43, Rob Weir robw...@apache.org wrote:
On Wed, Jun 5, 2013 at 11:34 AM, janI
Hi,
sorry for top-posting, but I think it makes sense to clean up some things.
Some facts and my opinions:
(1)
Fact: In communication with infra, infra had proposed
https://updates.openoffice.org/ (https://ooo-updates.openoffice.org/ as
the backup) as the URL for the resources accessed by the
On 5 June 2013 11:05, Oliver-Rainer Wittmann orwittm...@googlemail.comwrote:
Hi,
sorry for top-posting, but I think it makes sense to clean up some things.
Some facts and my opinions:
(1)
Fact: In communication with infra, infra had proposed
https://updates.openoffice.**org/
On Wed, Jun 5, 2013 at 11:34 AM, janI j...@apache.org wrote:
On 5 June 2013 16:48, Rob Weir robw...@apache.org wrote:
On Wed, Jun 5, 2013 at 10:32 AM, janI j...@apache.org wrote:
On 5 June 2013 11:05, Oliver-Rainer Wittmann orwittm...@googlemail.com
wrote:
Hi,
sorry for top-posting,
On Wed, Jun 5, 2013 at 10:03 AM, janI j...@apache.org wrote:
On 5 June 2013 18:37, Kay Schenk kay.sch...@gmail.com wrote:
On Wed, Jun 5, 2013 at 8:50 AM, janI j...@apache.org wrote:
On 5 June 2013 17:43, Rob Weir robw...@apache.org wrote:
On Wed, Jun 5, 2013 at 11:34 AM, janI
On Jun 5, 2013, at 12:37 PM, Kay Schenk kay.sch...@gmail.com wrote:
On Wed, Jun 5, 2013 at 8:50 AM, janI j...@apache.org wrote:
On 5 June 2013 17:43, Rob Weir robw...@apache.org wrote:
On Wed, Jun 5, 2013 at 11:34 AM, janI j...@apache.org wrote:
On 5 June 2013 16:48, Rob Weir
On 03/06/2013 Rob Weir wrote:
I think the concern is this:
1) We want SSL for 4.0.http://update.openoffice.org is not HTTPS.
2) The URL https://ooo-site.openoffice.apache.org supports SSL, but is
not considered long term stable. The URL is an artifact of the CMS
3) We're looking for a stable
On 4 June 2013 22:36, Andrea Pescetti pesce...@apache.org wrote:
On 03/06/2013 Rob Weir wrote:
I think the concern is this:
1) We want SSL for
4.0.http://update.openoffice.**orghttp://update.openoffice.org is not
HTTPS.
2) The URL
On Tue, Jun 4, 2013 at 5:59 PM, janI j...@apache.org wrote:
On 4 June 2013 22:36, Andrea Pescetti pesce...@apache.org wrote:
On 03/06/2013 Rob Weir wrote:
I think the concern is this:
1) We want SSL for
4.0.http://update.openoffice.**orghttp://update.openoffice.org is not
HTTPS.
2) The
I should mention also that we have a BZ issue tracking this required
change. It is categorized as a Release Blocker, so we don't forget
it:
https://issues.apache.org/ooo/show_bug.cgi?id=122444
-Rob
On Tue, Jun 4, 2013 at 6:05 PM, Rob Weir robw...@apache.org wrote:
On Tue, Jun 4, 2013 at 5:59
On 5 June 2013 00:05, Rob Weir robw...@apache.org wrote:
On Tue, Jun 4, 2013 at 5:59 PM, janI j...@apache.org wrote:
On 4 June 2013 22:36, Andrea Pescetti pesce...@apache.org wrote:
On 03/06/2013 Rob Weir wrote:
I think the concern is this:
1) We want SSL for
On Mon, Jun 3, 2013 at 5:11 AM, Oliver-Rainer Wittmann
orwittm...@googlemail.com wrote:
Hi,
On 03.06.2013 13:50, janI wrote:
On 3 June 2013 11:43, Oliver-Rainer Wittmann orwittm...@googlemail.com*
*wrote:
Hi,
On 02.06.2013 16:43, janI wrote:
Hi.
I have asked by my infra
Hi,
On 02.06.2013 16:43, janI wrote:
Hi.
I have asked by my infra collegaues, to ensuere we (AOO) have consensus on
how to handle updates.openoffice.org
I nobody objects I will assume lazy consensus in 72 hours from now and
1) create trunk/ooo-site/upates
My understandings of the
On 3 June 2013 11:43, Oliver-Rainer Wittmann orwittm...@googlemail.comwrote:
Hi,
On 02.06.2013 16:43, janI wrote:
Hi.
I have asked by my infra collegaues, to ensuere we (AOO) have consensus on
how to handle updates.openoffice.org
I nobody objects I will assume lazy consensus in 72 hours
On Mon, Jun 3, 2013 at 8:11 AM, Oliver-Rainer Wittmann
orwittm...@googlemail.com wrote:
Hi,
On 03.06.2013 13:50, janI wrote:
On 3 June 2013 11:43, Oliver-Rainer Wittmann
orwittm...@googlemail.comwrote:
Hi,
On 02.06.2013 16:43, janI wrote:
Hi.
I have asked by my infra collegaues, to
On Sun, Jun 2, 2013 at 7:43 AM, janI j...@apache.org wrote:
Hi.
I have asked by my infra collegaues, to ensuere we (AOO) have consensus on
how to handle updates.openoffice.org
I nobody objects I will assume lazy consensus in 72 hours from now and
1) create trunk/ooo-site/upates
2) let
19 matches
Mail list logo
