Am 10/15/2016 12:49 AM, schrieb Marcus:
Am 10/15/2016 12:20 AM, schrieb Matthias Seidel:
On
https://projects.apache.org/project.html?openoffice
the release should also be updated.
"(The releases are taken from the listing in the DOAP)"
@Andrea:
You are listed as maintainer on the webpage. D
Am 10/15/2016 12:20 AM, schrieb Matthias Seidel:
On
https://projects.apache.org/project.html?openoffice
the release should also be updated.
"(The releases are taken from the listing in the DOAP)"
@Andrea:
You are listed as maintainer on the webpage. Do you still know what and
where to updat
On
https://projects.apache.org/project.html?openoffice
the release should also be updated.
"(The releases are taken from the listing in the DOAP)"
regards
Matthias
smime.p7s
Description: S/MIME Cryptographic Signature
Instead of Languages I rather would like to discuss overall
architecture. The initial Architecture has not been changed much since
it was introduced i think.
But over time the requirements I see in the code have changed. Solving
Requirements with code and without adjusting the architecture lea
Am 10/14/2016 01:19 AM, schrieb Keith N. McKenna:
Marcus wrote:
Am 10/13/2016 09:34 PM, schrieb Keith N. McKenna:
Marcus wrote:
Am 10/13/2016 08:18 PM, schrieb Keith N. McKenna:
With the announcement of the Release of version 4.1.3 that revision
should be added to Bugzilla so that bugs can be
OK, it is a technical restriction... That explains it.
However it looks weird (by coincidence). ;-)
regards
Matthias
Am 14.10.2016 um 20:18 schrieb Marcus:
> Am 10/14/2016 01:35 PM, schrieb Matthias Seidel:
>> Why is the announcement for 4.1.3 on
>>
>> https://blogs.apache.org/OOo/entry/announ
Am 10/14/2016 01:35 PM, schrieb Matthias Seidel:
Why is the announcement for 4.1.3 on
https://blogs.apache.org/OOo/entry/announcing_apache_openoffice_4_12 ?
the blog software cannot produce URLs with more than 32 characters. The
URL creation is taken from the headline. To avoid to produce the
This was discussed several times before.
I was initially against the idea as Java can call C++ code easily these
days (eg. JNA, BridJ), but changed my mind when I realized how developing
OpenOffice itself in C/C++ is very difficult, and how much effort is wasted
(portability (eg. Win64), problemat
On 10/14/2016 3:24 AM, iamsuhailans...@gmail.com wrote:
I have a suggestion that Apache should write OpenOffice using Java and Netbeans
platform.
Thanks for your suggestion.
There would certainly be major advantages to it being in Java. We could
do a single build for all platforms. Several fo
I have a suggestion that Apache should write OpenOffice using Java and Netbeans
platform.
Sent from Mail for Windows 10
Why is the announcement for 4.1.3 on
https://blogs.apache.org/OOo/entry/announcing_apache_openoffice_4_12 ?
Seems there is a mismatch in the numbering (same for 4.1.2 -> 4_11 and
for 4.1.1 -> 4_1)
Can we just copy
https://blogs.apache.org/OOo/entry/announcing_apache_openoffice_4_12
to
https:
On 14-10-2016 08:01, Andrea Pescetti wrote:
Keith N. McKenna wrote:
Pedro wrote:
Currently version 4.1.2 still reports that it "is up to date"
I have added the your comment to the cwiki document. The change to the
update script is usually done several days after the formal Release
announceme
+1 ;-)
Am 14.10.2016 um 01:19 schrieb Keith N. McKenna:
> Marcus wrote:
>> Am 10/13/2016 09:34 PM, schrieb Keith N. McKenna:
>>> Marcus wrote:
Am 10/13/2016 08:18 PM, schrieb Keith N. McKenna:
> With the announcement of the Release of version 4.1.3 that revision
> should be added to
Keith N. McKenna wrote:
Pedro wrote:
Currently version 4.1.2 still reports that it "is up to date"
I have added the your comment to the cwiki document. The change to the
update script is usually done several days after the formal Release
announcement so as to minimize the load on the mirrors.
14 matches
Mail list logo