RE: Test Release 4.2.0-dev-m1 - SDBC-Bridge

2019-09-11 Thread Jan-Christian Wienandt
Moin,

I have the SDBC interface of release 4.2.0-dev-m1
tested with different database servers.

In addition to the respective JDBC connection, an ODBC connection was also
tested.

Here is a supplement to the link on MariaDB:

Using MYSQL-driver 8.0 the connection runs cleanly.
I was able to find out that it was a general problem
with the ODBC driver from MariaDB and OpenOffice / LibreOffice.

This bug affects all OpenOffice releases.

The result is available at the following link.
http://www.wienandt.de/download/test/Testing_SDBC.zip

 I hope it helps.


 Jan



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



Re: Test Release 4.2.0-dev-m1 - SDBC-Bridge

2019-05-23 Thread Matthias Seidel
Hi Jan,

Am 23.05.19 um 00:25 schrieb Jan-Christian Wienandt:
> Moin,
>
>  
>
> I have the SDBC interface of release 4.2.0-dev-m1 
>
> tested with different database servers.
>
>  
>
> In addition to the respective JDBC connection, an ODBC connection was also
> tested.
>
>  
>
> The result is available at the following link.
>
>  
>
>  <http://www.wienandt.de/download/test/Testing_SDBC.zip>
> http://www.wienandt.de/download/test/Testing_SDBC.zip
You're welcome!
>
>  
>
> I hope it helps.
Database is not my "area of expertise" but maybe Damjan (and Mechtilde?)
can have a look at it?
>
>  
>
> Excused my English

No need to excuse. ;-)

Regards,

   Matthias

>
>  
>
> Jan
>
>



smime.p7s
Description: S/MIME Cryptographic Signature


Test Release 4.2.0-dev-m1 - SDBC-Bridge

2019-05-22 Thread Jan-Christian Wienandt
Moin,

 

I have the SDBC interface of release 4.2.0-dev-m1 

tested with different database servers.

 

In addition to the respective JDBC connection, an ODBC connection was also
tested.

 

The result is available at the following link.

 

 <http://www.wienandt.de/download/test/Testing_SDBC.zip>
http://www.wienandt.de/download/test/Testing_SDBC.zip

 

I hope it helps.

 

Excused my English

 

Jan



Re: Release 4.2.0-dev-m1

2019-05-21 Thread Matthias Seidel
Moin Jan,

Am 21.05.19 um 21:52 schrieb Jan-Christian Wienandt:
> Moin Liste,
>
>  
>
> ich habe die neue SDBC-Schnittstelle mit unterschiedlichen Datenbankservern
> getestet.
>
> Die Tests liefen ausschließlich unter Windows über JDBC und ODBC.
>
>  
>
> Das Ergebnis findet Ihr hier:
>
>  
>
> http://www.wienandt.de/download/test/Testing_SDBC.zip
>
>  
>
> Vielleicht gibt es da noch Ideen / Tipps.
>
>  
>
> Linux (Debian) muss ich noch testen, wenn denn Zeit ist.
>
>  
>
> Eine Übersetzung ins englische und anschließender Veröffentlichung auf
>
> der internationalen dev-Liste folgt noch.
>
>  
>
> Was mir noch aufgefallen ist, dass sich einige Extensionen, wie der
> Report-Builder,
>
> nicht installieren lassen.

https://bz.apache.org/ooo/show_bug.cgi?id=128094

Hat irgendetwas mit der UNO-Schnittstelle zu tun. In der Deutschen
Version stockt es beim aktivieren des Französischen Wörterbuchs, meist
ist dann auch das Italienische nicht verfügbar.

Der Report-Builder scheint am gleichen Problem zu scheitern.

Wäre schön, wenn mehr Leute das testen/bestätigen könnten.

Meine (mehr oder weniger) regelmäßigen Builds für Windows sind hier zu
finden:
https://home.apache.org/~mseidel/AOO-builds/

Gruß,

   Matthias

>
>  
>
>  
>
> Gruß
>
> Jan
>
>  
>
>



smime.p7s
Description: S/MIME Cryptographic Signature


Release 4.2.0-dev-m1

2019-05-21 Thread Jan-Christian Wienandt
Moin Liste,

 

ich habe die neue SDBC-Schnittstelle mit unterschiedlichen Datenbankservern
getestet.

Die Tests liefen ausschließlich unter Windows über JDBC und ODBC.

 

Das Ergebnis findet Ihr hier:

 

http://www.wienandt.de/download/test/Testing_SDBC.zip

 

Vielleicht gibt es da noch Ideen / Tipps.

 

Linux (Debian) muss ich noch testen, wenn denn Zeit ist.

 

Eine Übersetzung ins englische und anschließender Veröffentlichung auf

der internationalen dev-Liste folgt noch.

 

Was mir noch aufgefallen ist, dass sich einige Extensionen, wie der
Report-Builder,

nicht installieren lassen.

 

 

Gruß

Jan

 



Re: Linux desktop integration an Dev builds (Was: Re: 4.2.0-dev-m1)

2019-04-05 Thread Jim Jagielski
yeah... for some reason, openoffice.lst is not parsed (or the results of such 
parsing) are not available at some stages of the build process, meaning that 
the Dev and Beta specific names are not honored. I'm trying to various things 
but none are elegant :(

> On Apr 5, 2019, at 1:39 PM, Matthias Seidel  
> wrote:
> 
> Hi Jim,
> 
> Am 04.04.19 um 20:14 schrieb Jim Jagielski:
>> Linux 64bit builds for en-US and de (both dpkg and rpm) can
>> be found at:
>> 
>>http://home.apache.org/~jim/AOO-builds/Dev-r1856914/
>> 
>> These SHOULD fix the desktop integration issues with Linux
>> builds when building Dev and/or Beta releases.
> 
> I can confirm what Pedro observed.
> 
> Additionally, we have a mix of names for the packages, come are
> "aoodev-..." some are "openoffice-developer-build-..."
> 
> Regards,
> 
>Matthias
> 
>> 
>> Please try asap and let me know how these work. TIA!
>> 
>> -
>> 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: Linux desktop integration an Dev builds (Was: Re: 4.2.0-dev-m1)

2019-04-05 Thread Matthias Seidel
Hi Jim,

Am 04.04.19 um 20:14 schrieb Jim Jagielski:
> Linux 64bit builds for en-US and de (both dpkg and rpm) can
> be found at:
>
> http://home.apache.org/~jim/AOO-builds/Dev-r1856914/
>
> These SHOULD fix the desktop integration issues with Linux
> builds when building Dev and/or Beta releases.

I can confirm what Pedro observed.

Additionally, we have a mix of names for the packages, come are
"aoodev-..." some are "openoffice-developer-build-..."

Regards,

   Matthias

>
> Please try asap and let me know how these work. TIA!
>
> -
> 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: Linux desktop integration an Dev builds (Was: Re: 4.2.0-dev-m1)

2019-04-05 Thread Jim Jagielski



> On Apr 4, 2019, at 5:31 PM, Pedro Lino  wrote:
> 
> Hi Jim, all
> 
>> Linux 64bit builds for en-US and de (both dpkg and rpm) can
>> be found at:
>> 
>>http://home.apache.org/~jim/AOO-builds/Dev-r1856914/
>> 
>> These SHOULD fix the desktop integration issues with Linux
>> builds when building Dev and/or Beta releases.
> 
> Unfortunately it is not completely fixed. The desktop-integration folder is 
> there, and the expected deb file is in it but the name seems to be wrong 
> (shouldn't it be aoodev something?)
> The menu items aren't added to Gnome so something else needs to be fixed...
> Can you compile the 4.1.0 Beta for Linux x64 and share the binaries?
> http://archive.apache.org/dist/openoffice/4.1.0-beta/source/
> I think this might help
> 

Thx for testing and the feedback...

Yeah, the issue is that some of those names seem hardcoded into
the various makefiles and scripts that implement desktop (system)
integration because the variables defined in OpenOffice.lst aren't
available. This is the case w/ both the Beta and the Dev builds.

Let me work on it more.


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



Re: Linux desktop integration an Dev builds (Was: Re: 4.2.0-dev-m1)

2019-04-04 Thread Pedro Lino
Hi Jim, all

> Linux 64bit builds for en-US and de (both dpkg and rpm) can
> be found at:
> 
> http://home.apache.org/~jim/AOO-builds/Dev-r1856914/
> 
> These SHOULD fix the desktop integration issues with Linux
> builds when building Dev and/or Beta releases.

Unfortunately it is not completely fixed. The desktop-integration folder is 
there, and the expected deb file is in it but the name seems to be wrong 
(shouldn't it be aoodev something?)
The menu items aren't added to Gnome so something else needs to be fixed...
Can you compile the 4.1.0 Beta for Linux x64 and share the binaries?
http://archive.apache.org/dist/openoffice/4.1.0-beta/source/
I think this might help

Regards,
Pedro

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



Linux desktop integration an Dev builds (Was: Re: 4.2.0-dev-m1)

2019-04-04 Thread Jim Jagielski
Linux 64bit builds for en-US and de (both dpkg and rpm) can
be found at:

http://home.apache.org/~jim/AOO-builds/Dev-r1856914/

These SHOULD fix the desktop integration issues with Linux
builds when building Dev and/or Beta releases.

Please try asap and let me know how these work. TIA!

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



Re: 4.2.0-dev-m1

2019-04-04 Thread Jim Jagielski



> On Apr 3, 2019, at 1:23 PM, Matthias Seidel  
> wrote:
> 
> Hi Jim,
> 
> Am 03.04.19 um 17:03 schrieb Jim Jagielski:
>> Do our Betas implement desktop integration?
> I really don't know (for Linux), I only tested Beta builds on Windows.
>> There is a var in openoffice.lst called ADDSYSTEMINTEGRATION which
>> is set to 1 for real builds and 0 for Beta builds and
>> missing for Dev builds.
> 
> Why haven't I seen that? It sounds reasonable, we should set it to 1 for
> Beta, add it for Dev and try again.
> 

We are getting closer... With that var set to 1, we error out with:

Error: ERROR: Source path not found for 
openoffice_developer_build-desktop-integration.tar.gz!

Note that the filename is "openoffice_developer_build..." but what we actually
build is openoffice-desktop-integration.tar.gz

I seem to recall in one of the desktop integration makefiles that
the filenames used don't have "access" to the one in OpenOffice.lst
so I have some ideas here to work around it.
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: 4.2.0-dev-m1

2019-04-03 Thread Matthias Seidel
Hi Jim,

Am 03.04.19 um 17:03 schrieb Jim Jagielski:
> Do our Betas implement desktop integration?
I really don't know (for Linux), I only tested Beta builds on Windows.
> There is a var in openoffice.lst called ADDSYSTEMINTEGRATION which
> is set to 1 for real builds and 0 for Beta builds and
> missing for Dev builds.

Why haven't I seen that? It sounds reasonable, we should set it to 1 for
Beta, add it for Dev and try again.

Regards,

   Matthias

>
> -
> 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: 4.2.0-dev-m1

2019-04-03 Thread Jim Jagielski
Do our Betas implement desktop integration? There is
a var in openoffice.lst called ADDSYSTEMINTEGRATION which
is set to 1 for real builds and 0 for Beta builds and
missing for Dev builds.

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



Re: 4.2.0-dev-m1

2019-04-02 Thread Matthias Seidel
Hi Jim,

Am 02.04.19 um 14:18 schrieb Jim Jagielski:
> Any feedback yet?

Unfortunately my changes didn't solve this issue. I am out of ideas...

What is missing from the tar.gz (full installation) is a folder called
"desktop-integration" containing something like "openoffice ...
-debian-menus_ ... _all.deb" (on Debian/Ubuntu). So menus and file
associations can not be created.

Other than that everything is working as expected.

Regards,

   Matthias

>
>> On Apr 1, 2019, at 10:57 AM, Jim Jagielski  wrote:
>>
>> Linux64 bit builds for de and en-US (dpkg and rpm) can be found at
>>
>>http://home.apache.org/~jim/AOO-builds/
>>
>> these are builds of AOO42X HEAD and just to check that
>> desktop integration is fixed.
>>
>> -
>> 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
>



smime.p7s
Description: S/MIME Cryptographic Signature


Re: 4.2.0-dev-m1

2019-04-02 Thread Jim Jagielski
Any feedback yet?

> On Apr 1, 2019, at 10:57 AM, Jim Jagielski  wrote:
> 
> Linux64 bit builds for de and en-US (dpkg and rpm) can be found at
> 
>http://home.apache.org/~jim/AOO-builds/
> 
> these are builds of AOO42X HEAD and just to check that
> desktop integration is fixed.
> 
> -
> 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: 4.2.0-dev-m1

2019-04-01 Thread Matthias Seidel
Am 01.04.19 um 13:01 schrieb Jim Jagielski:
> Which languages should I post for people to try?

My personal preferences would be en-US and de.

Matthias

>
>> On Mar 31, 2019, at 10:59 AM, Matthias Seidel  
>> wrote:
>>
>> Am 31.03.19 um 16:56 schrieb Jim Jagielski:
>>> Give me a few hours :)
>> No hurry, I am just curious if it works... ;-)
>>> -
>>> 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
>



smime.p7s
Description: S/MIME Cryptographic Signature


Re: 4.2.0-dev-m1

2019-04-01 Thread Jim Jagielski
Which languages should I post for people to try?

> On Mar 31, 2019, at 10:59 AM, Matthias Seidel  
> wrote:
> 
> Am 31.03.19 um 16:56 schrieb Jim Jagielski:
>> Give me a few hours :)
> No hurry, I am just curious if it works... ;-)
>> 
>> -
>> 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: 4.2.0-dev-m1

2019-03-31 Thread Matthias Seidel
Am 31.03.19 um 16:56 schrieb Jim Jagielski:
> Give me a few hours :)
No hurry, I am just curious if it works... ;-)
>
> -
> 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: 4.2.0-dev-m1

2019-03-31 Thread Jim Jagielski
Give me a few hours :)

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



Re: 4.2.0-dev-m1

2019-03-31 Thread Matthias Seidel
Hi Jim,

Am 29.03.19 um 12:23 schrieb Jim Jagielski:
> Does the lack of desktop integration in m1 mean that this dev release is DOA?

Can you do a Linux build based on r1856556 and see if the desktop
integration is included now?

https://svn.apache.org/viewvc?view=revision=1856556

Regards,

   Matthias

>
>
> -
> 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: 4.2.0-dev-m1

2019-03-30 Thread Matthias Seidel
Hi Peter,

Am 30.03.19 um 14:13 schrieb Peter Kovacs:
> added the below List to the cWiki.
>
> I add a connection from the 4.2.0 Release page. Maybe we can create an
> overview of tasks related.

Good idea!

Should we also add the most annoying bugs from Bugzilla there?

Matthias

>
> https://cwiki.apache.org/confluence/display/OOOUSERS/Open+List+from+Discussion
>
> On 30.03.19 11:09, Damjan Jovanovic wrote:
>> 1. Library audit.
>> 1.1 Did we lose or gain any public symbols in our libraries since the
>> 4.1.0? Gbuild requires explicit export instead of exporting everything and
>> then possibly controlling visibility with a .map file, so it's very
>> possible.
>> 1.2 Did ELF symbol versions on *nix platforms change? The older gbuild
>> modules probably did, as I didn't understand the meaning of .map files back
>> then.
>> 1.3 Are the same libraries with the same names available in both 4.1.0 and
>> 4.2.0?
>> 2. Base:
>> 2.1 Complete the Java SDBC driver framework, used by both the new SDBC-JDBC
>> bridge and the Postgres SDBC driver.
>> 2.2 Audit the new SDBC-JDBC bridge in Java against the old C++ one, fix any
>> differences.
>> 2.3 Complete the Postgres SDBC driver; still needs views, users, groups,
>> etc.
>> 2.4 Complete the integration of the Postgres SDBC driver into the Base UI
>> forms (like MySQL already is).
>> 3. Crashreporter
>> 3.1 Get it working again.
>> 3.2 Bug reported in UI form (instead of submitted to some now obsolete
>> server), which can be copied/pasted or attached to Bugzilla.
>> 4. Testing
>> 4.1 Run all available tests (unit tests, smoketest, module integration
>> tests, bvt, fvt, etc.) against 4.1.0 and 4.2.0, find and fix any
>> regressions.
> -
> 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: 4.2.0-dev-m1

2019-03-30 Thread Peter Kovacs
added the below List to the cWiki.

I add a connection from the 4.2.0 Release page. Maybe we can create an
overview of tasks related.

https://cwiki.apache.org/confluence/display/OOOUSERS/Open+List+from+Discussion

On 30.03.19 11:09, Damjan Jovanovic wrote:
> 1. Library audit.
> 1.1 Did we lose or gain any public symbols in our libraries since the
> 4.1.0? Gbuild requires explicit export instead of exporting everything and
> then possibly controlling visibility with a .map file, so it's very
> possible.
> 1.2 Did ELF symbol versions on *nix platforms change? The older gbuild
> modules probably did, as I didn't understand the meaning of .map files back
> then.
> 1.3 Are the same libraries with the same names available in both 4.1.0 and
> 4.2.0?
> 2. Base:
> 2.1 Complete the Java SDBC driver framework, used by both the new SDBC-JDBC
> bridge and the Postgres SDBC driver.
> 2.2 Audit the new SDBC-JDBC bridge in Java against the old C++ one, fix any
> differences.
> 2.3 Complete the Postgres SDBC driver; still needs views, users, groups,
> etc.
> 2.4 Complete the integration of the Postgres SDBC driver into the Base UI
> forms (like MySQL already is).
> 3. Crashreporter
> 3.1 Get it working again.
> 3.2 Bug reported in UI form (instead of submitted to some now obsolete
> server), which can be copied/pasted or attached to Bugzilla.
> 4. Testing
> 4.1 Run all available tests (unit tests, smoketest, module integration
> tests, bvt, fvt, etc.) against 4.1.0 and 4.2.0, find and fix any
> regressions.

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



Re: 4.2.0-dev-m1

2019-03-30 Thread Matthias Seidel
Hi Damjan,

Am 30.03.19 um 11:09 schrieb Damjan Jovanovic:
> >From my email on 15 February 2019:
>
> My own release checklist would include:
> 1. Library audit.
> 1.1 Did we lose or gain any public symbols in our libraries since the
> 4.1.0? Gbuild requires explicit export instead of exporting everything and
> then possibly controlling visibility with a .map file, so it's very
> possible.
> 1.2 Did ELF symbol versions on *nix platforms change? The older gbuild
> modules probably did, as I didn't understand the meaning of .map files back
> then.
> 1.3 Are the same libraries with the same names available in both 4.1.0 and
> 4.2.0?
> 2. Base:
> 2.1 Complete the Java SDBC driver framework, used by both the new SDBC-JDBC
> bridge and the Postgres SDBC driver.
> 2.2 Audit the new SDBC-JDBC bridge in Java against the old C++ one, fix any
> differences.
> 2.3 Complete the Postgres SDBC driver; still needs views, users, groups,
> etc.
> 2.4 Complete the integration of the Postgres SDBC driver into the Base UI
> forms (like MySQL already is).
> 3. Crashreporter
> 3.1 Get it working again.
> 3.2 Bug reported in UI form (instead of submitted to some now obsolete
> server), which can be copied/pasted or attached to Bugzilla.
> 4. Testing
> 4.1 Run all available tests (unit tests, smoketest, module integration
> tests, bvt, fvt, etc.) against 4.1.0 and 4.2.0, find and fix any
> regressions.
>
> ---
>
> So far, my library audit revealed a lot of symbol changes in some modules
> and a more detailed examination is necessary. Need to study ELF further to
> understand symbol versioning better. Also the GetVersionInfo symbol in UNO
> components is consistently missing when they are built by gbuild; dmake got
> it in by linking main/solenv/src/version.c into every library somehow, and
> gbuild should do the same.
>
> I've started some work on the Base stuff. To understand it better and get
> IDEs to play with it better, I am currently porting main/connectivity to
> gbuild. Still need to develop gbuild infrastructure to handle processing
> XCU/XCS configuration files with XSLT scripts, but many other modules need
> that too.

Thanks for all your work! It is highly appreciated.

Unfortunately all this is high above what I understand but I am
confident that other members will join the effort.

>
> Crashreporter involves complex interaction between code in main/sal and
> main/crashreporter, multiple files get generated and passed around. It
> shouldn't be too hard to get working though.

While I'd like to see crashreporter functional again in 4.2.X it must
not necessarily be in 4.2.0 but could come with a later (micro) release
(my opinion).

But the sooner the better.

>
> Nothing done regarding testing yet.

Apart from the automatic tests I want to add 3 major tasks:

1. QA
2. QA
3. QA

;-)

Regards,

   Matthias

>
> Damjan
>
>
> On Sat, Mar 30, 2019 at 11:32 AM Stehmann  wrote:
>
>> Hello
>>
>> Am 29. März 2019 19:40:47 MEZ schrieb Damjan Jovanovic >> :
>>> I have a lot of experience with desktop integration but am too busy to
>>> have
>>> a look.
>>>
>>> Also I posted a checklist of things we should do for the release. None
>>> of
>>> them are done yet.
>> Can you please post the list again
>>
>> Mechtilde
>>>
>>>
>>> On Fri, Mar 29, 2019 at 1:23 PM Jim Jagielski  wrote:
>>>
 Does the lack of desktop integration in m1 mean that this dev release
>>> is
 DOA?


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


>> --
>> Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
>>
>> -
>> 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: 4.2.0-dev-m1

2019-03-30 Thread Damjan Jovanovic
>From my email on 15 February 2019:

My own release checklist would include:
1. Library audit.
1.1 Did we lose or gain any public symbols in our libraries since the
4.1.0? Gbuild requires explicit export instead of exporting everything and
then possibly controlling visibility with a .map file, so it's very
possible.
1.2 Did ELF symbol versions on *nix platforms change? The older gbuild
modules probably did, as I didn't understand the meaning of .map files back
then.
1.3 Are the same libraries with the same names available in both 4.1.0 and
4.2.0?
2. Base:
2.1 Complete the Java SDBC driver framework, used by both the new SDBC-JDBC
bridge and the Postgres SDBC driver.
2.2 Audit the new SDBC-JDBC bridge in Java against the old C++ one, fix any
differences.
2.3 Complete the Postgres SDBC driver; still needs views, users, groups,
etc.
2.4 Complete the integration of the Postgres SDBC driver into the Base UI
forms (like MySQL already is).
3. Crashreporter
3.1 Get it working again.
3.2 Bug reported in UI form (instead of submitted to some now obsolete
server), which can be copied/pasted or attached to Bugzilla.
4. Testing
4.1 Run all available tests (unit tests, smoketest, module integration
tests, bvt, fvt, etc.) against 4.1.0 and 4.2.0, find and fix any
regressions.

---

So far, my library audit revealed a lot of symbol changes in some modules
and a more detailed examination is necessary. Need to study ELF further to
understand symbol versioning better. Also the GetVersionInfo symbol in UNO
components is consistently missing when they are built by gbuild; dmake got
it in by linking main/solenv/src/version.c into every library somehow, and
gbuild should do the same.

I've started some work on the Base stuff. To understand it better and get
IDEs to play with it better, I am currently porting main/connectivity to
gbuild. Still need to develop gbuild infrastructure to handle processing
XCU/XCS configuration files with XSLT scripts, but many other modules need
that too.

Crashreporter involves complex interaction between code in main/sal and
main/crashreporter, multiple files get generated and passed around. It
shouldn't be too hard to get working though.

Nothing done regarding testing yet.

Damjan


On Sat, Mar 30, 2019 at 11:32 AM Stehmann  wrote:

> Hello
>
> Am 29. März 2019 19:40:47 MEZ schrieb Damjan Jovanovic  >:
> >I have a lot of experience with desktop integration but am too busy to
> >have
> >a look.
> >
> >Also I posted a checklist of things we should do for the release. None
> >of
> >them are done yet.
>
> Can you please post the list again
>
> Mechtilde
> >
> >
> >
> >On Fri, Mar 29, 2019 at 1:23 PM Jim Jagielski  wrote:
> >
> >> Does the lack of desktop integration in m1 mean that this dev release
> >is
> >> DOA?
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >>
> >>
>
> --
> Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


Re: 4.2.0-dev-m1

2019-03-30 Thread Stehmann
Hello

Am 29. März 2019 19:40:47 MEZ schrieb Damjan Jovanovic :
>I have a lot of experience with desktop integration but am too busy to
>have
>a look.
>
>Also I posted a checklist of things we should do for the release. None
>of
>them are done yet.

Can you please post the list again

Mechtilde 
>
>
>
>On Fri, Mar 29, 2019 at 1:23 PM Jim Jagielski  wrote:
>
>> Does the lack of desktop integration in m1 mean that this dev release
>is
>> DOA?
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>>

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

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



Re: 4.2.0-dev-m1

2019-03-29 Thread Marcus

Am 29.03.19 um 17:15 schrieb Matthias Seidel:

Am 29.03.19 um 12:23 schrieb Jim Jagielski:

Does the lack of desktop integration in m1 mean that this dev release is DOA?


Not in my (personal) opinion.

After all, this is a developer build and people should know how to start
it from commandline or how to create a shortcut.
Of course we should fix it for the next build.


correct, for a dev build far away from a show stopper. So, lets use the 
train model *) in  such cases.


*) When a commit doesn't succeed to get in time into the next 
build/release (train) then it has to take the next one.


Marcus


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



Re: 4.2.0-dev-m1

2019-03-29 Thread Matthias Seidel
Hi Damjan,

Am 29.03.19 um 19:40 schrieb Damjan Jovanovic:
> I have a lot of experience with desktop integration but am too busy to have
> a look.
I have committed a change to "openoffice.lst" that hopefully fixes this
issue for the Developer build.
>
> Also I posted a checklist of things we should do for the release. None of
> them are done yet.

That's why we now only have a (first) Developer Build. ;-)

Bug hunting and fixing is needed, as well as translation for all languages.
Every help is welcome!

Regards,

   Matthias

>
>
>
> On Fri, Mar 29, 2019 at 1:23 PM Jim Jagielski  wrote:
>
>> Does the lack of desktop integration in m1 mean that this dev release is
>> DOA?
>>
>>
>> -
>> 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: 4.2.0-dev-m1

2019-03-29 Thread Damjan Jovanovic
I have a lot of experience with desktop integration but am too busy to have
a look.

Also I posted a checklist of things we should do for the release. None of
them are done yet.



On Fri, Mar 29, 2019 at 1:23 PM Jim Jagielski  wrote:

> Does the lack of desktop integration in m1 mean that this dev release is
> DOA?
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


Re: 4.2.0-dev-m1

2019-03-29 Thread Stehmann
+1

Am 29. März 2019 17:15:50 MEZ schrieb Matthias Seidel 
:
>Am 29.03.19 um 12:23 schrieb Jim Jagielski:
>> Does the lack of desktop integration in m1 mean that this dev release
>is DOA?
>
>Not in my (personal) opinion.
>
>After all, this is a developer build and people should know how to
>start
>it from commandline or how to create a shortcut.
>Of course we should fix it for the next build.
>
>Matthias
>
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

Re: 4.2.0-dev-m1

2019-03-29 Thread Matthias Seidel
Am 29.03.19 um 12:23 schrieb Jim Jagielski:
> Does the lack of desktop integration in m1 mean that this dev release is DOA?

Not in my (personal) opinion.

After all, this is a developer build and people should know how to start
it from commandline or how to create a shortcut.
Of course we should fix it for the next build.

Matthias

>
>
> -
> 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: 4.2.0-dev-m1

2019-03-29 Thread Stehmann
IMO we should take it as a first Dev build. See my other comment too


Am 29. März 2019 12:23:15 MEZ schrieb Jim Jagielski :
>Does the lack of desktop integration in m1 mean that this dev release
>is DOA?
>
>
>-
>To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>For additional commands, e-mail: dev-h...@openoffice.apache.org

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

4.2.0-dev-m1

2019-03-29 Thread Jim Jagielski
Does the lack of desktop integration in m1 mean that this dev release is DOA?


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