FOSDEM

[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


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Suggestion

[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.


I do not have to believe in the client in order to support this. I just
have to be curious where other OpenOffice modules could benefit from
features an email client would bring.

And then is the trick to do this right. I have already some ideas.


BTW, we use a lot of dynamic libraries. This is a clear hint that
OpenOffice is not monolithic. Just the Architecture is not understood,
or wrong designed / used.

A monolithic build would only consist of static linked libraries.
(According to the book Clean Architecture)


All the best

Peter

On 28.01.19 00:25, Andrea Pescetti wrote:
> Peter Kovacs wrote:
>> I think the request for a OpenOffice Mail Client has been placed
>> repeatedly over time.
>
> Yes, but it is due to a misleading analogy with what Microsoft does
> (or used to do) by incorporating a mail client into their Office suite.
>
> The main mission of OpenOffice focuses on office productivity, and I
> think we are still good at that. The code is very monolithic and an
> external solution (Thunderbird being a natural choice) is more or less
> the only option that makes sense.
>
>> To be clear: This is a more year effort.
>
> E-mail has moved to the cloud much faster than office productivity.
> Honestly, if we ever were to announce that OpenOffice would start
> actions for including a mail client in the (not immediate) future,
> this would be irrelevant to most people even among our own users.
>
> In short, I think adding an e-mail client never made sense, and that
> this was irrelevant even when it was actually in the suite (not named
> OpenOffice yet), but it is even more irrelevant now.
>
> If someone is going to join to help with creating an e-mail module, it
> would be better to put those energies to better use.
>
> Regards,
>   Andrea.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Time for our first 4.2.0 beta?

[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, 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. ;-)

 It is "our" second: ;-)

 https://archive.apache.org/dist/openoffice/4.1.0-beta/
>>>
>>> OK, this is a bit embarrassing. ;-)
>>>
> I would say we should not do things different (at least not too many)
> compared to our normal releases.
>
> After thinking a bit I suggest that we:
>
> - exchange the splash screen with a big and clear hint that it's a
> beta (no production use, no regular support, etc.)
>>>
>>> When we had already a Beta release then this must be somewhere.
>>
>> See below.
>>
>> I already made an early test build for a Beta some time ago...
>
> sorry, actually I meant the about box. Do we have also for this a
> special graphic and text content?

There are beta graphics [1] [2] [3] and the text can be changed via
configure switch (as we do with our buildbots)

As I wrote, the appropriate graphics are used by building the beta targets.

Matthias

[1]
https://svn.apache.org/repos/asf/openoffice/branches/AOO42X/main/default_images/introabout/beta/about.png
[2]
https://svn.apache.org/repos/asf/openoffice/branches/AOO42X/main/default_images/introabout/beta/intro.png
[3]
https://svn.apache.org/repos/asf/openoffice/branches/AOO42X/main/default_images/framework/res/beta/backing.png

>
> Marcus
>
>
>
> - prepare the install files as a normal release but with special file
> names
 A build with the special targets (openofficebeta, sdkoobeta,
 ooobetalanguagepack) will do this automatically.
> - no participation with the update service

 --disable-online-update in configure.

> - upload the install files to SourceForge in an own subdir
> - offer them on our download webpage

 If the download page can handle that, it would be perfect.
>>>
>>> I think it's a matter of time to get this integrated. But should be
>>> faster than the test phase for the Beta itself.
>>
>> Personally, I don't think we are at Beta stage already... But we
>> definitely have to work towards it! ;-)
>>
>> Matthias
>>
>>>
>>> Marcus
>>>
>>>
>>>
> I don't know how we can to collect the feedback. BZ is not the right
> channel for this. Can we create a special beta area in the forums?
> What I mean is, is there enough coverage of moderators and power
> users?
>
> Marcus
>
>
>
>>> 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 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 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 other thoughts?
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Remove main/crashrep?

[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 removed? That would free some space
and remove unused strings for translation.

Regards,

   Matthias




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Time for our first 4.2.0 beta?

[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?
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. ;-)


It is "our" second: ;-)

https://archive.apache.org/dist/openoffice/4.1.0-beta/


OK, this is a bit embarrassing. ;-)


I would say we should not do things different (at least not too many)
compared to our normal releases.

After thinking a bit I suggest that we:

- exchange the splash screen with a big and clear hint that it's a
beta (no production use, no regular support, etc.)


When we had already a Beta release then this must be somewhere.


See below.

I already made an early test build for a Beta some time ago...


sorry, actually I meant the about box. Do we have also for this a 
special graphic and text content?


Marcus




- prepare the install files as a normal release but with special file
names

A build with the special targets (openofficebeta, sdkoobeta,
ooobetalanguagepack) will do this automatically.

- no participation with the update service


--disable-online-update in configure.


- upload the install files to SourceForge in an own subdir
- offer them on our download webpage


If the download page can handle that, it would be perfect.


I think it's a matter of time to get this integrated. But should be
faster than the test phase for the Beta itself.


Personally, I don't think we are at Beta stage already... But we
definitely have to work towards it! ;-)

Matthias



Marcus




I don't know how we can to collect the feedback. BZ is not the right
channel for this. Can we create a special beta area in the forums?
What I mean is, is there enough coverage of moderators and power users?

Marcus




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 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 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 other thoughts?



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Time for our first 4.2.0 beta?

[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 years old now.

>
> I am happy on the progress.
So am I.
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Time for our first 4.2.0 beta?

[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 unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Time for our first 4.2.0 beta?

[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 English could be gathered on the appropriate forums, though they may
need to make a dedicated area. It would be nice to widen the range of
participants beyond people comfortable in English.

I am not sure what the concern is behind the comment "What I mean is, is
there enough coverage of moderators and power users?". On the en forum we
have close to 24 hour coverage of moderators and volunteers and I don't
think an increase in traffic from a beta build would be a problem. The es
forum is the only other one I have experience with and I think there are
plenty of moderators and volunteers there to handle an increase in traffic,
though I obviously have not asked them about this.

I would be happy to make note on this list of interesting or repeated input
about a beta build appearing on the en or es forums.

Stating the correct way to give feedback on the Splash screen should be
considered.

best regards,
Francis

On Mon, Jan 28, 2019 at 12:53 PM Marcus  wrote:

> 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 would say we should not do things different (at least not too many)
> compared to our normal releases.
>
> After thinking a bit I suggest that we:
>
> - exchange the splash screen with a big and clear hint that it's a beta
> (no production use, no regular support, etc.)
> - prepare the install files as a normal release but with special file names
> - no participation with the update service
> - upload the install files to SourceForge in an own subdir
> - offer them on our download webpage
>
> I don't know how we can to collect the feedback. BZ is not the right
> channel for this. Can we create a special beta area in the forums? What
> I mean is, is there enough coverage of moderators and power users?
>
> Marcus
>
>
>
> >> 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 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 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 other thoughts?
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Re: Time for our first 4.2.0 beta?

[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?
>>>
>>> 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. ;-)
>>
>> It is "our" second: ;-)
>>
>> https://archive.apache.org/dist/openoffice/4.1.0-beta/
>
> OK, this is a bit embarrassing. ;-)
>
>>> I would say we should not do things different (at least not too many)
>>> compared to our normal releases.
>>>
>>> After thinking a bit I suggest that we:
>>>
>>> - exchange the splash screen with a big and clear hint that it's a
>>> beta (no production use, no regular support, etc.)
>
> When we had already a Beta release then this must be somewhere.

See below.

I already made an early test build for a Beta some time ago...

>
>>> - prepare the install files as a normal release but with special file
>>> names
>> A build with the special targets (openofficebeta, sdkoobeta,
>> ooobetalanguagepack) will do this automatically.
>>> - no participation with the update service
>>
>> --disable-online-update in configure.
>>
>>> - upload the install files to SourceForge in an own subdir
>>> - offer them on our download webpage
>>
>> If the download page can handle that, it would be perfect.
>
> I think it's a matter of time to get this integrated. But should be
> faster than the test phase for the Beta itself.

Personally, I don't think we are at Beta stage already... But we
definitely have to work towards it! ;-)

Matthias

>
> Marcus
>
>
>
>>> I don't know how we can to collect the feedback. BZ is not the right
>>> channel for this. Can we create a special beta area in the forums?
>>> What I mean is, is there enough coverage of moderators and power users?
>>>
>>> Marcus
>>>
>>>
>>>
> 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 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 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 other thoughts?
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Time for our first 4.2.0 beta?

[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
tell you what to do / where to go and we have to find the way
together. ;-)


It is "our" second: ;-)

https://archive.apache.org/dist/openoffice/4.1.0-beta/


OK, this is a bit embarrassing. ;-)


I would say we should not do things different (at least not too many)
compared to our normal releases.

After thinking a bit I suggest that we:

- exchange the splash screen with a big and clear hint that it's a
beta (no production use, no regular support, etc.)


When we had already a Beta release then this must be somewhere.


- prepare the install files as a normal release but with special file
names

A build with the special targets (openofficebeta, sdkoobeta,
ooobetalanguagepack) will do this automatically.

- no participation with the update service


--disable-online-update in configure.


- upload the install files to SourceForge in an own subdir
- offer them on our download webpage


If the download page can handle that, it would be perfect.


I think it's a matter of time to get this integrated. But should be 
faster than the test phase for the Beta itself.


Marcus




I don't know how we can to collect the feedback. BZ is not the right
channel for this. Can we create a special beta area in the forums?
What I mean is, is there enough coverage of moderators and power users?

Marcus




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 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 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 other thoughts?



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Time for our first 4.2.0 beta?

[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 last preparations to do, so my time is limited until early
next week...

Regards,

   Matthias

>> 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 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 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 other thoughts?
>>>
>>
>> -- 
>> Mechtilde Stehmann
>> ## Apache OpenOffice
>> ## Freie Office Suite für Linux, MacOSX, Windows
>> ## Debian Developer
>> ## PGP encryption welcome
>> ## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Time for our first 4.2.0 beta?

[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 / where to go and we have to find the way
> together. ;-)

It is "our" second: ;-)

https://archive.apache.org/dist/openoffice/4.1.0-beta/

>
> I would say we should not do things different (at least not too many)
> compared to our normal releases.
>
> After thinking a bit I suggest that we:
>
> - exchange the splash screen with a big and clear hint that it's a
> beta (no production use, no regular support, etc.)
> - prepare the install files as a normal release but with special file
> names
A build with the special targets (openofficebeta, sdkoobeta,
ooobetalanguagepack) will do this automatically.
> - no participation with the update service

--disable-online-update in configure.

> - upload the install files to SourceForge in an own subdir
> - offer them on our download webpage

If the download page can handle that, it would be perfect.

Matthias

>
> I don't know how we can to collect the feedback. BZ is not the right
> channel for this. Can we create a special beta area in the forums?
> What I mean is, is there enough coverage of moderators and power users?
>
> Marcus
>
>
>
>>> 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 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 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 other thoughts?
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Time for our first 4.2.0 beta?

[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 would say we should not do things different (at least not too many) 
compared to our normal releases.


After thinking a bit I suggest that we:

- exchange the splash screen with a big and clear hint that it's a beta 
(no production use, no regular support, etc.)

- prepare the install files as a normal release but with special file names
- no participation with the update service
- upload the install files to SourceForge in an own subdir
- offer them on our download webpage

I don't know how we can to collect the feedback. BZ is not the right 
channel for this. Can we create a special beta area in the forums? What 
I mean is, is there enough coverage of moderators and power users?


Marcus




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 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 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 other thoughts?



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Time for our first 4.2.0 beta?

[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 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 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 other thoughts?
>> 
> 
> 
> -- 
> Mechtilde Stehmann
> ## Apache OpenOffice
> ## Freie Office Suite für Linux, MacOSX, Windows
> ## Debian Developer
> ## PGP encryption welcome
> ## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F
> 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Time for our first 4.2.0 beta?

[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 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 other thoughts?
> 


-- 
Mechtilde Stehmann
## Apache OpenOffice
## Freie Office Suite für Linux, MacOSX, Windows
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F



signature.asc
Description: OpenPGP digital signature

Re: Using AOO 4.2-dev with Java 11

[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),
  o up to and including Java 8 it was possible to force invocation of 
methods using
setAccessible() on all objects (unless an explicit security manager 
would prohibit this);
starting with the modularization one cannot pass by this restriction; 
however, if there are
access rights in a superclass to the desired method/field/constructor, 
then using that class
object's method, field and constructor objects would allow invocation 
on Java 9 and higher
as well),

  * no JRE anymore, the JDK (Java development kit) becomes the new JRE (pure 
Java applications can
create an adjusted runtime environment starting with Java 9).

---rony

P.S.: For testing various versions of Java on various operating systems a good 
place to look around
for it would be: .


On 27.01.2019 13:37, Mechtilde wrote:
> Hello,
>
> I tried to activate Java 11 with my AOO 4.2-dev build. this doesn't
> work. I get the message (translated back to English)
>
> The chosen directory dosn't contain a jre. Please choose another directory.
>
> I choose /usr/lib/jvm/java-11-openjdk-amd64/. In this directory ther eis
> no one named jre.
>
> It works with /usr/lib/jvm/java-8-openjdk-amd64/jre.
>
> so there is a need of some corrections for time there is no openjdk-8
> anymore.
>
> Kind regards

Re: Fwd: CLT2019/B184: Ausstellerzusage

[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 signature

Time for our first 4.2.0 beta?

[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 other thoughts?

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org