Am 01.10.19 um 10:33 schrieb Matthias Seidel:
Am 01.10.19 um 01:23 schrieb Marcus:
Am 30.09.19 um 22:59 schrieb Matthias Seidel:
Am 30.09.19 um 22:35 schrieb Peter Kovacs:
We had constant 7 votes on 4.1.7 and 4.1.6 release. However only 3
volunteers voted in both releases.
These numbers are low in general. Maybe we need to organize test
phases in order to raize the numbers. This will still not raise test
attendance for a single feature.
How about we schedule a test release every quarter? These releases
do not necessary lead to a release and are announced as unstable.
But it would give people a better time frame to plan and we can
advertise for tester.
I build new versions about every second week.
For sure, people are downloading these builds and use them on a daily
base. Still no feedback!
The problem isn't about the builds...
to make it a bit more comfortable for you: What about to build only
when it is worth it (e.g., after some commits or bigger/important
commits and not with a fixed time schedule?
I am not uncomfortable with building AOO. In fact I build even more
often to test my changes before I commit.
I only upload once a week or two. ;-)
And don't forget that we have no working buildbots anymore!
sure, I just want to show you a way to reduce your builds. Especially
when the commit rate is very low at the moment.
Marcus
Am 30. September 2019 21:13:52 MESZ schrieb Matthias Seidel
<matthias.sei...@hamburg.de>:
Hi Dave,
Am 30.09.19 um 18:53 schrieb Dave Fisher:
Hi Matthias,
I think that it is likely people were focused on 4.1.7 testing.
Where have all these people been when we voted for release? ;-)
My personal opinion is that if switching does not require users to
switch and they can use the Oracle JRE if that is what they have then
the change make sense.
The user is still free to choose whatever JRE he/she wants (and is
detected by AOO).
I build with AdoptOpenJDK for some weeks now [1] and have found no
problems. But that *really* needs more testing...
Regards,
Matthias
[1] https://home.apache.org/~mseidel/AOO-builds/AOO-420-Test/
Regards,
Dave
On Sep 30, 2019, at 8:31 AM, Matthias Seidel
<matthias.sei...@hamburg.de> wrote:
No feedback=No interest?
Maybe I should stop providing test builds.
That would save me a lot of my spare time...
Regards,
Matthias
Am 05.09.19 um 12:58 schrieb Matthias Seidel:
Hi Keith, all,
Did you have time to test?
Feedback is always welcome... ;-)
Regards,
Matthias
Am 01.09.19 um 18:23 schrieb Matthias Seidel:
Hi all,
Am 31.08.19 um 18:45 schrieb Matthias Seidel:
Hi Keith,
Am 31.08.19 um 15:37 schrieb Keith N. McKenna:
On 8/31/2019 4:23 AM, Matthias Seidel wrote:
Hi all,
At the moment I am doing my test builds (trunk and 42X) for
Windows with
the latest Oracle JDK (8u221).
I am still able to download, but Oracle changed its licensing.
I am not
a lawyer and would prefer to move away from it.
Damjan recently introduced some patches, so AOO can now work
with
AdoptOpenJDK.
It is available in 32 bit, which is still needed for Windows
[1].
I am just doing a build for AOO 4.2.0 with AdaptOpenJDK (8u222)
and it
looks good so far...
What do you think?
Regards,
Matthias
[1]
https://adoptopenjdk.net/releases.html?variant=openjdk8&jvmVariant=hotspot#x32_win
Mathias;
This sounds like it has great potential as it appears to gives
us a
potential path beyond version 8 as a cursory reading of the
AdoptOpenJDK
web site shows that it supports version 11 and 12 for both both
Windows
32 and 64 bit systems.
I look forward to testing your new version 4.2.0 build with the
AdoptOpenJDK.
You will find them at the usual place:
https://home.apache.org/~mseidel/AOO-builds/AOO-420-Test/
They should be up tomorrow.
Builds are online!
Please test, especially everything related to Java. ;-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
