> -Original Message-
> From: Dave Fisher [mailto:w...@apache.org]
> Sent: Wednesday, December 30, 2020 4:47 PM
> To: dev@openoffice.apache.org
> Subject: Re: Policy to deal with old web content - Archiving pages?
>
> The two websites are in a Git repository and changes can be
> rever
> -Original Message-
> From: Peter Kovacs [mailto:pe...@apache.org]
> Sent: Wednesday, December 30, 2020 11:06 AM
> To: dev@openoffice.apache.org
> Subject: Re: Policy to deal with old web content - Archiving pages?
>
>
> On 30.12.20 00:08, Dave Fisher wrote:
> >
> >> On Dec 29, 2020,
> -Original Message-
> From: Keith N. McKenna [mailto:keith.mcke...@comcast.net]
> Sent: Wednesday, December 30, 2020 9:12 PM
> To: dev@openoffice.apache.org
> Subject: Re: Policy to deal with old web content - Archiving pages?
>
> >> That may be the best way to proceed at the moment.
> -Original Message-
> From: Keith N. McKenna [mailto:keith.mcke...@comcast.net]
> Sent: Wednesday, December 30, 2020 9:42 PM
> To: dev@openoffice.apache.org
> Subject: Re: Policy to deal with old web content - Archiving pages?
> I agree entirely that archiving is a waste of time and effo
Hello,
I have described the current problematic situation regarding Big Sur and
explained why it is important to inform our users quickly and that there is no
time to wait for a new program release.
I opened a thread about "lazy consensus" and made concrete text suggestions for
the release not
Am 31.12.20 um 01:01 schrieb Matthias Seidel:
Am 31.12.20 um 00:46 schrieb Marcus:
As I haven't seen any veto-like negative statement the change is now
online.
However, any changes are still possible.
I would propose that we add some additional text for Windows and macOS.
It could be done sim
Hi Marcus,
Am 31.12.20 um 11:41 schrieb Marcus:
> Am 31.12.20 um 01:01 schrieb Matthias Seidel:
>> Am 31.12.20 um 00:46 schrieb Marcus:
>>> As I haven't seen any veto-like negative statement the change is now
>>> online.
>>>
>>> However, any changes are still possible.
>>
>> I would propose that w
Hello Jörg,
This is not how things are done. I read your mail as blackmail and toxic. Just
don't do such stuff. Actions like this puts the feeling on myself that I should
do something, because otherwise something 'wrong' will happen. I would rather
let you edit the page instead of giving you th
Am 31.12.20 um 11:50 schrieb Peter Kovacs:
This is not how things are done. I read your mail as blackmail and toxic. Just
don't do such stuff. Actions like this puts the feeling on myself that I should
do something, because otherwise something 'wrong' will happen. I would rather
let you edit t
> -Original Message-
> From: Peter Kovacs [mailto:pe...@apache.org]
> Sent: Thursday, December 31, 2020 11:51 AM
> To: dev@openoffice.apache.org
> Subject: Re: My last advance notice regarding Big Sur (was:
> What we should do now)
>
> Hello Jörg,
>
> This is not how things are done. I
Am 31.12.20 um 12:30 schrieb Jörg Schmidt:
-Original Message-
From: Peter Kovacs [mailto:pe...@apache.org]
Sent: Thursday, December 31, 2020 11:51 AM
To: dev@openoffice.apache.org
Subject: Re: My last advance notice regarding Big Sur (was:
What we should do now)
This is not how things ar
> -Original Message-
> From: Marcus [mailto:marcus.m...@wtnet.de]
> Sent: Thursday, December 31, 2020 12:00 PM
> To: dev@openoffice.apache.org
> Subject: Re: My last advance notice regarding Big Sur (was:
> What we should do now)
>
> Am 31.12.20 um 11:50 schrieb Peter Kovacs:
> > This is
> -Original Message-
> From: Marcus [mailto:marcus.m...@wtnet.de]
> Sent: Thursday, December 31, 2020 12:36 PM
> To: dev@openoffice.apache.org
> Subject: Re: My last advance notice regarding Big Sur (was:
> What we should do now)
>
> Am 31.12.20 um 12:30 schrieb Jörg Schmidt:
> >> -O
Great,
BTW I did some graphs on confluence wiki concerning the build perl script.
Dontbknow where exactly something with development.
Am 31. Dezember 2020 02:02:16 MEZ schrieb Steve Lubbs :
>Hi All,
>
>I've been spending quite a bit of time reverse engineering the
>threading
>and concurrency imp
> -Original Message-
> From: Marcus [mailto:marcus.m...@wtnet.de]
> Sent: Thursday, December 31, 2020 12:00 PM
> To: dev@openoffice.apache.org
> Subject: Re: My last advance notice regarding Big Sur (was:
> What we should do now)
> At the moment Christmas is over and the year end is near
> On Dec 31, 2020, at 5:06 AM, Jörg Schmidt wrote:
>
>
> Although it was clear to everyone here that the issue needs a quick solution,
> and although there were many discussion posts and a lot of hard work in
> revising the blogpost, nothing relevant has happened yet.
Are you crazy? Did yo
Goto https://GitHub.com/Apache/OpenOffice-org/ to enter the current website
“house”.
Read the docs and look at the branches. Educate yourself to the current
technical details.
Ask educated questions after Jan 1 in a single email in a new thread.
We also have the svn repos which has all the cha
On 12/31/2020 4:38 AM, Jörg Schmidt wrote:
>> -Original Message-
>> From: Keith N. McKenna [mailto:keith.mcke...@comcast.net]
>> Sent: Wednesday, December 30, 2020 9:42 PM
>> To: dev@openoffice.apache.org
>> Subject: Re: Policy to deal with old web content - Archiving pages?
>
>> I agree
> -Original Message-
> From: Dave Fisher [mailto:w...@apache.org]
> Sent: Thursday, December 31, 2020 3:25 PM
> To: dev@openoffice.apache.org
> Subject: Re: Policy to deal with old web content - Archiving pages?
>
> Goto https://GitHub.com/Apache/OpenOffice-org/ to enter the
> current
> -Original Message-
> From: Keith N. McKenna [mailto:keith.mcke...@comcast.net]
> Sent: Thursday, December 31, 2020 4:31 PM
> To: dev@openoffice.apache.org
> Subject: Re: Policy to deal with old web content - Archiving pages?
>
> On 12/31/2020 4:38 AM, Jörg Schmidt wrote:
> >> -Or
> -Original Message-
> From: Jim Jagielski [mailto:j...@jagunet.com]
> Sent: Thursday, December 31, 2020 3:19 PM
> To: dev
> Subject: Re: My last advance notice regarding Big Sur (was:
> What we should do now)
>
>
>
> > On Dec 31, 2020, at 5:06 AM, Jörg Schmidt
> wrote:
> >
> >
Please stop calling 4.1.9 a patch. It is a release which has fixes including
the one for the BigSur issue. We are following the same process we did for
4.1.8 which was released less than two months ago. That release took about a
month to work through all issues in the RCs.
This community effort
22 matches
Mail list logo
