FOSDEM

2019-01-28 Thread Peter Kovacs
Hello, I will not attend at FOSDEM. To much to do, and no responsibilities lead to this desicion. I am sorry. I hope next year it will be better. Instead I try to come to Chemnitz. I hope my life is quieter by then. All the Best Peter

Re: Suggestion

2019-01-28 Thread Peter Kovacs
I think OpenOffice is about developer freedom to do what he wants to do. If a someone shows up and wants to do an email client, then let him. Even if the project spins off into its own realm because there are only little things that both benefit from. I do not believe any harm is done by that.

Re: Time for our first 4.2.0 beta?

2019-01-28 Thread Matthias Seidel
Hi Marcus, Am 28.01.19 um 23:52 schrieb Marcus: > Am 28.01.19 um 21:32 schrieb Matthias Seidel: >> Am 28.01.19 um 21:23 schrieb Marcus: >>> Am 28.01.19 um 21:06 schrieb Matthias Seidel: Am 28.01.19 um 20:30 schrieb Marcus: > Am 28.01.19 um 19:39 schrieb Jim Jagielski: >> Perfect,

Remove main/crashrep?

2019-01-28 Thread Matthias Seidel
Hi all, The crash report tool was abandoned some years ago. Help files were removed in 2014: https://bz.apache.org/ooo/show_bug.cgi?id=125696 Now I simply removed the directory main/crashrep from my build tree (AOO42X) and still could build successfully. So my question is, can it be safely

Re: Time for our first 4.2.0 beta?

2019-01-28 Thread Marcus
Am 28.01.19 um 21:32 schrieb Matthias Seidel: Am 28.01.19 um 21:23 schrieb Marcus: Am 28.01.19 um 21:06 schrieb Matthias Seidel: Am 28.01.19 um 20:30 schrieb Marcus: Am 28.01.19 um 19:39 schrieb Jim Jagielski: Perfect, thx. Just so I know, what's the procedure for us doing beta releases?

Re: Time for our first 4.2.0 beta?

2019-01-28 Thread Matthias Seidel
Am 28.01.19 um 23:20 schrieb Peter Kovacs: > On 28.01.19 21:32, Matthias Seidel wrote: >> Personally, I don't think we are at Beta stage already... But we >> definitely have to work towards it! ;-) >> >> Matthias > > What is missing? I can simply crash it with two clicks... ;-) That bug is 4 1/2

Re: Time for our first 4.2.0 beta?

2019-01-28 Thread Peter Kovacs
On 28.01.19 21:32, Matthias Seidel wrote: > > Personally, I don't think we are at Beta stage already... But we > definitely have to work towards it! ;-) > > Matthias What is missing? I am happy on the progress. - To

Re: Time for our first 4.2.0 beta?

2019-01-28 Thread F C. Costero
I am a moderator on the en forum but I am speaking only for myself here. I think gathering feedback on the forum would be a good solution. The en forum has a User Experience area that gets very little traffic and could perhaps be used to gather beta build input. Feedback in languages other than

Re: Time for our first 4.2.0 beta?

2019-01-28 Thread Matthias Seidel
Am 28.01.19 um 21:23 schrieb Marcus: > Am 28.01.19 um 21:06 schrieb Matthias Seidel: >> Am 28.01.19 um 20:30 schrieb Marcus: >>> Am 28.01.19 um 19:39 schrieb Jim Jagielski: Perfect, thx. Just so I know, what's the procedure for us doing beta releases? Where do they go? >>> >>>

Re: Time for our first 4.2.0 beta?

2019-01-28 Thread Marcus
Am 28.01.19 um 21:06 schrieb Matthias Seidel: Am 28.01.19 um 20:30 schrieb Marcus: Am 28.01.19 um 19:39 schrieb Jim Jagielski: Perfect, thx. Just so I know, what's the procedure for us doing beta releases? Where do they go? this will be our first beta release here at Apache. So, nobody can

Re: Time for our first 4.2.0 beta?

2019-01-28 Thread Matthias Seidel
Hi Jim, Am 28.01.19 um 19:39 schrieb Jim Jagielski: > Perfect, thx. > > Just so I know, what's the procedure for us doing beta releases? Where do > they go? Just a general reminder: A bunch of people, including Mechtilde, Andrea and me will be at FOSDEM in Brussels next weekend. I have some

Re: Time for our first 4.2.0 beta?

2019-01-28 Thread Matthias Seidel
Hi Marcus, Am 28.01.19 um 20:30 schrieb Marcus: > Am 28.01.19 um 19:39 schrieb Jim Jagielski: >> Perfect, thx. >> >> Just so I know, what's the procedure for us doing beta releases? >> Where do they go? > > this will be our first beta release here at Apache. So, nobody can > tell you what to do /

Re: Time for our first 4.2.0 beta?

2019-01-28 Thread Marcus
Am 28.01.19 um 19:39 schrieb Jim Jagielski: Perfect, thx. Just so I know, what's the procedure for us doing beta releases? Where do they go? this will be our first beta release here at Apache. So, nobody can tell you what to do / where to go and we have to find the way together. ;-) I

Re: Time for our first 4.2.0 beta?

2019-01-28 Thread Jim Jagielski
Perfect, thx. Just so I know, what's the procedure for us doing beta releases? Where do they go? > On Jan 28, 2019, at 12:31 PM, Mechtilde wrote: > > Hello Jim, > > the beta version should contain the recent translation, so I will start > to prepare an update of the *.sdf files. > > Kind

Re: Time for our first 4.2.0 beta?

2019-01-28 Thread Mechtilde
Hello Jim, the beta version should contain the recent translation, so I will start to prepare an update of the *.sdf files. Kind regards Am 28.01.19 um 14:20 schrieb Jim Jagielski: > I think we are at a stage where we should consider doing our > 1st beta release of 4.2.0... we have successful

Re: Using AOO 4.2-dev with Java 11

2019-01-28 Thread Rony G. Flatscher (Apache)
Starting with Java 9 (the same is true for Java 11, just pointing out the first version that may exhibit this behaviour) there are at least two important changes: * modularisation (with the effect that setAccessible() will not work anymore if applied to objects from non-exported modules),

Re: Fwd: CLT2019/B184: Ausstellerzusage

2019-01-28 Thread Dr. Michael Stehmann
Hallo, Am 26.01.19 um 11:15 schrieb Matthias Seidel: > P.S.: Kann der Freedom-Bus nicht kurz über Hamburg fahren? ;-) > Wenn Du genug Mitfahrer findest (gegebenenfalls auch auf der Strecke nach Chemnitz), sage ich Birgit Bescheid. Gruß Michael signature.asc Description: OpenPGP digital

Time for our first 4.2.0 beta?

2019-01-28 Thread Jim Jagielski
I think we are at a stage where we should consider doing our 1st beta release of 4.2.0... we have successful builds for macOS, Linux 32 and 64, and Windows; we have a stable 4.2.0-dev branch, and enough changes to warrant a beta release for testing and feedback (all IMO ;) ). Any comments or