Re: Test builds of AOO 4.1.6 HEAD

2018-10-21 Thread Peter kovacs 
Stupid question where is the script?

Am 21. Oktober 2018 23:58:25 MESZ schrieb Matthias Seidel 
:
>Am 21.10.18 um 23:55 schrieb Marcus:
>> Am 21.10.2018 um 23:27 schrieb Matthias Seidel:
>>> Am 21.10.18 um 22:43 schrieb Peter kovacs:

 When the year issue has been fixed, I think we can call it an RC1.
>I
 check tomorrow evening. Sorry had no energy for stuff on the
>weekend.
>>>
>>> How do we want to sign the builds?
>>>
>>> "For new releases, PMCs MUST supply SHA-256 and/or SHA-512; and
>SHOULD
>>> NOT supply MD5 or SHA-1" [1]
>>>
>>> My suggestion would be to only supply SHA512.
>>
>> I don't see a problem to support also SHA256. And it's less work to
>> re-write the download scripting.
>
>OK, then someone has to work on the signing script... ;-)
>
>Matthias
>
>>
>> Marcus
>>
>>
>>
>>> Signatures and checksums could be generated with:
>>>
>https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/hash-sign-512.sh
>>>
>>>
>>> [1] https://www.apache.org/dev/release-distribution#sigs-and-sums
>>>
 Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel
 :
> Am 21.10.18 um 20:08 schrieb Marcus:
>> Am 21.10.2018 um 20:06 schrieb Matthias Seidel:
>>> Am 21.10.18 um 19:59 schrieb Marcus:
 Am 20.10.2018 um 20:02 schrieb Jim Jagielski:
> That's what it looks like, yeah.
 copyright years are always forgotten to update. Every year the
> same.
 ;-)
>>> In fact I *did* update it for trunk in January... ;-)
>> hm, OK. Are you sure that you have updated it everywhere it is
> needed?
>> Even here the script could be helpful.
> I did update it where we always(TM) updated it:
> https://svn.apache.org/viewvc?view=revisionrevision=1780015
>
> But there are several parts (ODK, Linux packaging) which should
>get
> some
> attention.
> In 4.1.x they were not updated in all these years...
>
> So +1 for a script from me!
>
> Matthias
>
>> Marcus
>>
>>
>>
>>> But my test build are always with --with-vendor in configure, so
>I
>>> didn't realize that it was missing from branch 4.1.6.
>>>
>>> Matthias
>>>
 We now have a script to update version numbers; somewhere in
>the
 devtools I think.

 What about to create a new script to list all the code lines
>with a
 the year number. Then someone can have a look and compare it
>with
> the
 current calendar year and if needed create a patch to update
>all
 affected year numbers at ones.

 Maybe a good first step because no year number is forgotten.
>The
> next
 one would be to automate this update. But I've not yet an idea
>how
> to
 do this.

 What do you think?

 Marcus



>> On Oct 20, 2018, at 11:20 AM, Matthias Seidel
>>  wrote:
>>
>> Am 20.10.18 um 17:16 schrieb Jim Jagielski:
>>> Found it.
>> Great!
>>> Fixed in r1844422 and r1844423
>> That means, when using --vendor it is updated automatically,
>> otherwise not?
>>
 On Oct 20, 2018, at 10:54 AM, Jim Jagielski
>
 wrote:

 Are we sure that that part of the splash screen isn't
>hardcoded
> in
 (ie: the Copyright part)?

 I know that I use '--with-vendor="Apache OpenOffice
>Community
 Build" \' for macOS and I am guessing the buildbots also
>use
> that
 configure option, so maybe that's a clue.

> On Oct 20, 2018, at 9:45 AM, Pedro Lino
> 
> wrote:
>
> That is probably because your OS is named Darwin (more
> evolved?) :)
>
>
>
> 
>
>
>
>> On October 20, 2018 at 2:35 PM Jim Jagielski
> 
>> wrote:
>>
>> Hmmm... The macOS builds are showing 2018:
>>
>> 
>>
>>> On Oct 20, 2018, at 7:14 AM, Pedro Lino <
>>> pedro.l...@mailbox.org >
> wrote:
     But even if I wanted, I can not change the
>copyright
> year...
     That's what I am wondering about. ;-)

>>> Ok. I (wrongly) assumed it was all editable :)
>>>
>>>
     BTW: Can you confirm 2017 as copyright year in
>Jim's
> Linux
 builds?


>>> Yes, Jim's build is showing 2017.
>>>
>>>
>>> Regards,
>>>
>>> Pedro
>>
>>
>> -
>> To unsubscribe, e-mail:

Re: Test builds of AOO 4.1.6 HEAD

2018-10-21 Thread Matthias Seidel 
Am 21.10.18 um 23:55 schrieb Marcus:
> Am 21.10.2018 um 23:27 schrieb Matthias Seidel:
>> Am 21.10.18 um 22:43 schrieb Peter kovacs:
>>>
>>> When the year issue has been fixed, I think we can call it an RC1. I
>>> check tomorrow evening. Sorry had no energy for stuff on the weekend.
>>
>> How do we want to sign the builds?
>>
>> "For new releases, PMCs MUST supply SHA-256 and/or SHA-512; and SHOULD
>> NOT supply MD5 or SHA-1" [1]
>>
>> My suggestion would be to only supply SHA512.
>
> I don't see a problem to support also SHA256. And it's less work to
> re-write the download scripting.

OK, then someone has to work on the signing script... ;-)

Matthias

>
> Marcus
>
>
>
>> Signatures and checksums could be generated with:
>> https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/hash-sign-512.sh
>>
>>
>> [1] https://www.apache.org/dev/release-distribution#sigs-and-sums
>>
>>> Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel
>>> :
 Am 21.10.18 um 20:08 schrieb Marcus:
> Am 21.10.2018 um 20:06 schrieb Matthias Seidel:
>> Am 21.10.18 um 19:59 schrieb Marcus:
>>> Am 20.10.2018 um 20:02 schrieb Jim Jagielski:
 That's what it looks like, yeah.
>>> copyright years are always forgotten to update. Every year the
 same.
>>> ;-)
>> In fact I *did* update it for trunk in January... ;-)
> hm, OK. Are you sure that you have updated it everywhere it is
 needed?
> Even here the script could be helpful.
 I did update it where we always(TM) updated it:
 https://svn.apache.org/viewvc?view=revisionrevision=1780015

 But there are several parts (ODK, Linux packaging) which should get
 some
 attention.
 In 4.1.x they were not updated in all these years...

 So +1 for a script from me!

 Matthias

> Marcus
>
>
>
>> But my test build are always with --with-vendor in configure, so I
>> didn't realize that it was missing from branch 4.1.6.
>>
>> Matthias
>>
>>> We now have a script to update version numbers; somewhere in the
>>> devtools I think.
>>>
>>> What about to create a new script to list all the code lines with a
>>> the year number. Then someone can have a look and compare it with
 the
>>> current calendar year and if needed create a patch to update all
>>> affected year numbers at ones.
>>>
>>> Maybe a good first step because no year number is forgotten. The
 next
>>> one would be to automate this update. But I've not yet an idea how
 to
>>> do this.
>>>
>>> What do you think?
>>>
>>> Marcus
>>>
>>>
>>>
> On Oct 20, 2018, at 11:20 AM, Matthias Seidel
>  wrote:
>
> Am 20.10.18 um 17:16 schrieb Jim Jagielski:
>> Found it.
> Great!
>> Fixed in r1844422 and r1844423
> That means, when using --vendor it is updated automatically,
> otherwise not?
>
>>> On Oct 20, 2018, at 10:54 AM, Jim Jagielski 
>>> wrote:
>>>
>>> Are we sure that that part of the splash screen isn't hardcoded
 in
>>> (ie: the Copyright part)?
>>>
>>> I know that I use '--with-vendor="Apache OpenOffice Community
>>> Build" \' for macOS and I am guessing the buildbots also use
 that
>>> configure option, so maybe that's a clue.
>>>
 On Oct 20, 2018, at 9:45 AM, Pedro Lino
 
 wrote:

 That is probably because your OS is named Darwin (more
 evolved?) :)



 



> On October 20, 2018 at 2:35 PM Jim Jagielski
 
> wrote:
>
> Hmmm... The macOS builds are showing 2018:
>
> 
>
>> On Oct 20, 2018, at 7:14 AM, Pedro Lino <
>> pedro.l...@mailbox.org >
 wrote:
>>>     But even if I wanted, I can not change the copyright
 year...
>>>     That's what I am wondering about. ;-)
>>>
>> Ok. I (wrongly) assumed it was all editable :)
>>
>>
>>>     BTW: Can you confirm 2017 as copyright year in Jim's
 Linux
>>> builds?
>>>
>>>
>> Yes, Jim's build is showing 2017.
>>
>>
>> Regards,
>>
>> Pedro
>
>
> -
> 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: Test builds of AOO 4.1.6 HEAD

2018-10-21 Thread Marcus 

Am 21.10.2018 um 22:43 schrieb Peter kovacs:


When the year issue has been fixed, I think we can call it an RC1. I check 
tomorrow evening. Sorry had no energy for stuff on the weekend.


just to prevent misunderstandings:

My suggestion was a general improvement and not limited to this release. 
Of course the 4.1.6 should not wait for this.


Marcus




Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel 
:

Am 21.10.18 um 20:08 schrieb Marcus:

Am 21.10.2018 um 20:06 schrieb Matthias Seidel:

Am 21.10.18 um 19:59 schrieb Marcus:

Am 20.10.2018 um 20:02 schrieb Jim Jagielski:

That's what it looks like, yeah.


copyright years are always forgotten to update. Every year the

same.

;-)


In fact I *did* update it for trunk in January... ;-)


hm, OK. Are you sure that you have updated it everywhere it is

needed?

Even here the script could be helpful.


I did update it where we always(TM) updated it:
https://svn.apache.org/viewvc?view=revisionrevision=1780015

But there are several parts (ODK, Linux packaging) which should get
some
attention.
In 4.1.x they were not updated in all these years...

So +1 for a script from me!

Matthias



Marcus




But my test build are always with --with-vendor in configure, so I
didn't realize that it was missing from branch 4.1.6.

Matthias



We now have a script to update version numbers; somewhere in the
devtools I think.

What about to create a new script to list all the code lines with a
the year number. Then someone can have a look and compare it with

the

current calendar year and if needed create a patch to update all
affected year numbers at ones.

Maybe a good first step because no year number is forgotten. The

next

one would be to automate this update. But I've not yet an idea how

to

do this.

What do you think?

Marcus




On Oct 20, 2018, at 11:20 AM, Matthias Seidel
 wrote:

Am 20.10.18 um 17:16 schrieb Jim Jagielski:

Found it.

Great!


Fixed in r1844422 and r1844423


That means, when using --vendor it is updated automatically,
otherwise not?




On Oct 20, 2018, at 10:54 AM, Jim Jagielski 
wrote:

Are we sure that that part of the splash screen isn't hardcoded

in

(ie: the Copyright part)?

I know that I use '--with-vendor="Apache OpenOffice Community
Build" \' for macOS and I am guessing the buildbots also use

that

configure option, so maybe that's a clue.


On Oct 20, 2018, at 9:45 AM, Pedro Lino



wrote:

That is probably because your OS is named Darwin (more
evolved?) :)








On October 20, 2018 at 2:35 PM Jim Jagielski



wrote:

Hmmm... The macOS builds are showing 2018:




On Oct 20, 2018, at 7:14 AM, Pedro Lino <
pedro.l...@mailbox.org >

wrote:



    But even if I wanted, I can not change the copyright

year...

    That's what I am wondering about. ;-)


Ok. I (wrongly) assumed it was all editable :)



    BTW: Can you confirm 2017 as copyright year in Jim's

Linux

builds?



Yes, Jim's build is showing 2017.


Regards,

Pedro



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

Re: Test builds of AOO 4.1.6 HEAD

2018-10-21 Thread Marcus 

Am 21.10.2018 um 23:27 schrieb Matthias Seidel:

Am 21.10.18 um 22:43 schrieb Peter kovacs:


When the year issue has been fixed, I think we can call it an RC1. I check 
tomorrow evening. Sorry had no energy for stuff on the weekend.


How do we want to sign the builds?

"For new releases, PMCs MUST supply SHA-256 and/or SHA-512; and SHOULD
NOT supply MD5 or SHA-1" [1]

My suggestion would be to only supply SHA512.


I don't see a problem to support also SHA256. And it's less work to 
re-write the download scripting.


Marcus




Signatures and checksums could be generated with:
https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/hash-sign-512.sh

[1] https://www.apache.org/dev/release-distribution#sigs-and-sums


Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel 
:

Am 21.10.18 um 20:08 schrieb Marcus:

Am 21.10.2018 um 20:06 schrieb Matthias Seidel:

Am 21.10.18 um 19:59 schrieb Marcus:

Am 20.10.2018 um 20:02 schrieb Jim Jagielski:

That's what it looks like, yeah.

copyright years are always forgotten to update. Every year the

same.

;-)

In fact I *did* update it for trunk in January... ;-)

hm, OK. Are you sure that you have updated it everywhere it is

needed?

Even here the script could be helpful.

I did update it where we always(TM) updated it:
https://svn.apache.org/viewvc?view=revisionrevision=1780015

But there are several parts (ODK, Linux packaging) which should get
some
attention.
In 4.1.x they were not updated in all these years...

So +1 for a script from me!

Matthias


Marcus




But my test build are always with --with-vendor in configure, so I
didn't realize that it was missing from branch 4.1.6.

Matthias


We now have a script to update version numbers; somewhere in the
devtools I think.

What about to create a new script to list all the code lines with a
the year number. Then someone can have a look and compare it with

the

current calendar year and if needed create a patch to update all
affected year numbers at ones.

Maybe a good first step because no year number is forgotten. The

next

one would be to automate this update. But I've not yet an idea how

to

do this.

What do you think?

Marcus




On Oct 20, 2018, at 11:20 AM, Matthias Seidel
 wrote:

Am 20.10.18 um 17:16 schrieb Jim Jagielski:

Found it.

Great!

Fixed in r1844422 and r1844423

That means, when using --vendor it is updated automatically,
otherwise not?


On Oct 20, 2018, at 10:54 AM, Jim Jagielski 
wrote:

Are we sure that that part of the splash screen isn't hardcoded

in

(ie: the Copyright part)?

I know that I use '--with-vendor="Apache OpenOffice Community
Build" \' for macOS and I am guessing the buildbots also use

that

configure option, so maybe that's a clue.


On Oct 20, 2018, at 9:45 AM, Pedro Lino



wrote:

That is probably because your OS is named Darwin (more
evolved?) :)








On October 20, 2018 at 2:35 PM Jim Jagielski



wrote:

Hmmm... The macOS builds are showing 2018:




On Oct 20, 2018, at 7:14 AM, Pedro Lino <
pedro.l...@mailbox.org >

wrote:

    But even if I wanted, I can not change the copyright

year...

    That's what I am wondering about. ;-)


Ok. I (wrongly) assumed it was all editable :)



    BTW: Can you confirm 2017 as copyright year in Jim's

Linux

builds?



Yes, Jim's build is showing 2017.


Regards,

Pedro



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

Re: Test builds of AOO 4.1.6 HEAD

2018-10-21 Thread Matthias Seidel 
Hi Peter,

Am 21.10.18 um 22:43 schrieb Peter kovacs:
> Hi all.
>
> When the year issue has been fixed, I think we can call it an RC1. I check 
> tomorrow evening. Sorry had no energy for stuff on the weekend.

How do we want to sign the builds?

"For new releases, PMCs MUST supply SHA-256 and/or SHA-512; and SHOULD
NOT supply MD5 or SHA-1" [1]

My suggestion would be to only supply SHA512.

Signatures and checksums could be generated with:
https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/hash-sign-512.sh

Regards,

   Matthias

[1] https://www.apache.org/dev/release-distribution#sigs-and-sums

>
> All the best
>  Peter
>
> Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel 
> :
>> Am 21.10.18 um 20:08 schrieb Marcus:
>>> Am 21.10.2018 um 20:06 schrieb Matthias Seidel:
 Am 21.10.18 um 19:59 schrieb Marcus:
> Am 20.10.2018 um 20:02 schrieb Jim Jagielski:
>> That's what it looks like, yeah.
> copyright years are always forgotten to update. Every year the
>> same.
> ;-)
 In fact I *did* update it for trunk in January... ;-)
>>> hm, OK. Are you sure that you have updated it everywhere it is
>> needed?
>>> Even here the script could be helpful.
>> I did update it where we always(TM) updated it:
>> https://svn.apache.org/viewvc?view=revisionrevision=1780015
>>
>> But there are several parts (ODK, Linux packaging) which should get
>> some
>> attention.
>> In 4.1.x they were not updated in all these years...
>>
>> So +1 for a script from me!
>>
>> Matthias
>>
>>> Marcus
>>>
>>>
>>>
 But my test build are always with --with-vendor in configure, so I
 didn't realize that it was missing from branch 4.1.6.

 Matthias

> We now have a script to update version numbers; somewhere in the
> devtools I think.
>
> What about to create a new script to list all the code lines with a
> the year number. Then someone can have a look and compare it with
>> the
> current calendar year and if needed create a patch to update all
> affected year numbers at ones.
>
> Maybe a good first step because no year number is forgotten. The
>> next
> one would be to automate this update. But I've not yet an idea how
>> to
> do this.
>
> What do you think?
>
> Marcus
>
>
>
>>> On Oct 20, 2018, at 11:20 AM, Matthias Seidel
>>>  wrote:
>>>
>>> Am 20.10.18 um 17:16 schrieb Jim Jagielski:
 Found it.
>>> Great!
 Fixed in r1844422 and r1844423
>>> That means, when using --vendor it is updated automatically,
>>> otherwise not?
>>>
> On Oct 20, 2018, at 10:54 AM, Jim Jagielski 
> wrote:
>
> Are we sure that that part of the splash screen isn't hardcoded
>> in
> (ie: the Copyright part)?
>
> I know that I use '--with-vendor="Apache OpenOffice Community
> Build" \' for macOS and I am guessing the buildbots also use
>> that
> configure option, so maybe that's a clue.
>
>> On Oct 20, 2018, at 9:45 AM, Pedro Lino
>> 
>> wrote:
>>
>> That is probably because your OS is named Darwin (more
>> evolved?) :)
>>
>>
>>
>> 
>>
>>
>>
>>> On October 20, 2018 at 2:35 PM Jim Jagielski
>> 
>>> wrote:
>>>
>>> Hmmm... The macOS builds are showing 2018:
>>>
>>> 
>>>
 On Oct 20, 2018, at 7:14 AM, Pedro Lino <
 pedro.l...@mailbox.org >
>> wrote:
>    But even if I wanted, I can not change the copyright
>> year...
>    That's what I am wondering about. ;-)
>
 Ok. I (wrongly) assumed it was all editable :)


>    BTW: Can you confirm 2017 as copyright year in Jim's
>> Linux
> builds?
>
>
 Yes, Jim's build is showing 2017.


 Regards,

 Pedro
>>>
>>> -
>>> 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: Test builds of AOO 4.1.6 HEAD

2018-10-21 Thread Peter kovacs 
Hi all.

When the year issue has been fixed, I think we can call it an RC1. I check 
tomorrow evening. Sorry had no energy for stuff on the weekend.

All the best
 Peter

Am 21. Oktober 2018 20:19:53 MESZ schrieb Matthias Seidel 
:
>Am 21.10.18 um 20:08 schrieb Marcus:
>> Am 21.10.2018 um 20:06 schrieb Matthias Seidel:
>>> Am 21.10.18 um 19:59 schrieb Marcus:
 Am 20.10.2018 um 20:02 schrieb Jim Jagielski:
> That's what it looks like, yeah.

 copyright years are always forgotten to update. Every year the
>same.
 ;-)
>>>
>>> In fact I *did* update it for trunk in January... ;-)
>>
>> hm, OK. Are you sure that you have updated it everywhere it is
>needed?
>> Even here the script could be helpful.
>
>I did update it where we always(TM) updated it:
>https://svn.apache.org/viewvc?view=revisionrevision=1780015
>
>But there are several parts (ODK, Linux packaging) which should get
>some
>attention.
>In 4.1.x they were not updated in all these years...
>
>So +1 for a script from me!
>
>Matthias
>
>>
>> Marcus
>>
>>
>>
>>> But my test build are always with --with-vendor in configure, so I
>>> didn't realize that it was missing from branch 4.1.6.
>>>
>>> Matthias
>>>

 We now have a script to update version numbers; somewhere in the
 devtools I think.

 What about to create a new script to list all the code lines with a
 the year number. Then someone can have a look and compare it with
>the
 current calendar year and if needed create a patch to update all
 affected year numbers at ones.

 Maybe a good first step because no year number is forgotten. The
>next
 one would be to automate this update. But I've not yet an idea how
>to
 do this.

 What do you think?

 Marcus



>> On Oct 20, 2018, at 11:20 AM, Matthias Seidel
>>  wrote:
>>
>> Am 20.10.18 um 17:16 schrieb Jim Jagielski:
>>> Found it.
>> Great!
>>>
>>> Fixed in r1844422 and r1844423
>>
>> That means, when using --vendor it is updated automatically,
>> otherwise not?
>>
>>>
 On Oct 20, 2018, at 10:54 AM, Jim Jagielski 
 wrote:

 Are we sure that that part of the splash screen isn't hardcoded
>in
 (ie: the Copyright part)?

 I know that I use '--with-vendor="Apache OpenOffice Community
 Build" \' for macOS and I am guessing the buildbots also use
>that
 configure option, so maybe that's a clue.

> On Oct 20, 2018, at 9:45 AM, Pedro Lino
>
> wrote:
>
> That is probably because your OS is named Darwin (more
> evolved?) :)
>
>
>
> 
>
>
>
>> On October 20, 2018 at 2:35 PM Jim Jagielski
>
>> wrote:
>>
>> Hmmm... The macOS builds are showing 2018:
>>
>> 
>>
>>> On Oct 20, 2018, at 7:14 AM, Pedro Lino <
>>> pedro.l...@mailbox.org >
>wrote:
>>>
    But even if I wanted, I can not change the copyright
>year...
    That's what I am wondering about. ;-)

>>> Ok. I (wrongly) assumed it was all editable :)
>>>
>>>
    BTW: Can you confirm 2017 as copyright year in Jim's
>Linux
 builds?


>>> Yes, Jim's build is showing 2017.
>>>
>>>
>>> Regards,
>>>
>>> Pedro
>>
>>
>> -
>> 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: Test builds of AOO 4.1.6 HEAD

2018-10-21 Thread Matthias Seidel 
Am 21.10.18 um 20:08 schrieb Marcus:
> Am 21.10.2018 um 20:06 schrieb Matthias Seidel:
>> Am 21.10.18 um 19:59 schrieb Marcus:
>>> Am 20.10.2018 um 20:02 schrieb Jim Jagielski:
 That's what it looks like, yeah.
>>>
>>> copyright years are always forgotten to update. Every year the same.
>>> ;-)
>>
>> In fact I *did* update it for trunk in January... ;-)
>
> hm, OK. Are you sure that you have updated it everywhere it is needed?
> Even here the script could be helpful.

I did update it where we always(TM) updated it:
https://svn.apache.org/viewvc?view=revisionrevision=1780015

But there are several parts (ODK, Linux packaging) which should get some
attention.
In 4.1.x they were not updated in all these years...

So +1 for a script from me!

Matthias

>
> Marcus
>
>
>
>> But my test build are always with --with-vendor in configure, so I
>> didn't realize that it was missing from branch 4.1.6.
>>
>> Matthias
>>
>>>
>>> We now have a script to update version numbers; somewhere in the
>>> devtools I think.
>>>
>>> What about to create a new script to list all the code lines with a
>>> the year number. Then someone can have a look and compare it with the
>>> current calendar year and if needed create a patch to update all
>>> affected year numbers at ones.
>>>
>>> Maybe a good first step because no year number is forgotten. The next
>>> one would be to automate this update. But I've not yet an idea how to
>>> do this.
>>>
>>> What do you think?
>>>
>>> Marcus
>>>
>>>
>>>
> On Oct 20, 2018, at 11:20 AM, Matthias Seidel
>  wrote:
>
> Am 20.10.18 um 17:16 schrieb Jim Jagielski:
>> Found it.
> Great!
>>
>> Fixed in r1844422 and r1844423
>
> That means, when using --vendor it is updated automatically,
> otherwise not?
>
>>
>>> On Oct 20, 2018, at 10:54 AM, Jim Jagielski 
>>> wrote:
>>>
>>> Are we sure that that part of the splash screen isn't hardcoded in
>>> (ie: the Copyright part)?
>>>
>>> I know that I use '--with-vendor="Apache OpenOffice Community
>>> Build" \' for macOS and I am guessing the buildbots also use that
>>> configure option, so maybe that's a clue.
>>>
 On Oct 20, 2018, at 9:45 AM, Pedro Lino 
 wrote:

 That is probably because your OS is named Darwin (more
 evolved?) :)



 



> On October 20, 2018 at 2:35 PM Jim Jagielski 
> wrote:
>
> Hmmm... The macOS builds are showing 2018:
>
> 
>
>> On Oct 20, 2018, at 7:14 AM, Pedro Lino <
>> pedro.l...@mailbox.org > wrote:
>>
>>>    But even if I wanted, I can not change the copyright year...
>>>    That's what I am wondering about. ;-)
>>>
>> Ok. I (wrongly) assumed it was all editable :)
>>
>>
>>>    BTW: Can you confirm 2017 as copyright year in Jim's Linux
>>> builds?
>>>
>>>
>> Yes, Jim's build is showing 2017.
>>
>>
>> Regards,
>>
>> Pedro
>
>
> -
> 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: Test builds of AOO 4.1.6 HEAD

2018-10-21 Thread Marcus 

Am 21.10.2018 um 20:06 schrieb Matthias Seidel:

Am 21.10.18 um 19:59 schrieb Marcus:

Am 20.10.2018 um 20:02 schrieb Jim Jagielski:

That's what it looks like, yeah.


copyright years are always forgotten to update. Every year the same. ;-)


In fact I *did* update it for trunk in January... ;-)


hm, OK. Are you sure that you have updated it everywhere it is needed? 
Even here the script could be helpful.


Marcus




But my test build are always with --with-vendor in configure, so I
didn't realize that it was missing from branch 4.1.6.

Matthias



We now have a script to update version numbers; somewhere in the
devtools I think.

What about to create a new script to list all the code lines with a
the year number. Then someone can have a look and compare it with the
current calendar year and if needed create a patch to update all
affected year numbers at ones.

Maybe a good first step because no year number is forgotten. The next
one would be to automate this update. But I've not yet an idea how to
do this.

What do you think?

Marcus




On Oct 20, 2018, at 11:20 AM, Matthias Seidel
 wrote:

Am 20.10.18 um 17:16 schrieb Jim Jagielski:

Found it.

Great!


Fixed in r1844422 and r1844423


That means, when using --vendor it is updated automatically,
otherwise not?




On Oct 20, 2018, at 10:54 AM, Jim Jagielski  wrote:

Are we sure that that part of the splash screen isn't hardcoded in
(ie: the Copyright part)?

I know that I use '--with-vendor="Apache OpenOffice Community
Build" \' for macOS and I am guessing the buildbots also use that
configure option, so maybe that's a clue.


On Oct 20, 2018, at 9:45 AM, Pedro Lino 
wrote:

That is probably because your OS is named Darwin (more evolved?) :)








On October 20, 2018 at 2:35 PM Jim Jagielski 
wrote:

Hmmm... The macOS builds are showing 2018:




On Oct 20, 2018, at 7:14 AM, Pedro Lino <
pedro.l...@mailbox.org > wrote:


   But even if I wanted, I can not change the copyright year...
   That's what I am wondering about. ;-)


Ok. I (wrongly) assumed it was all editable :)



   BTW: Can you confirm 2017 as copyright year in Jim's Linux
builds?



Yes, Jim's build is showing 2017.


Regards,

Pedro



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

Re: Test builds of AOO 4.1.6 HEAD

2018-10-21 Thread Matthias Seidel 
Am 21.10.18 um 19:59 schrieb Marcus:
> Am 20.10.2018 um 20:02 schrieb Jim Jagielski:
>> That's what it looks like, yeah.
>
> copyright years are always forgotten to update. Every year the same. ;-)

In fact I *did* update it for trunk in January... ;-)

But my test build are always with --with-vendor in configure, so I
didn't realize that it was missing from branch 4.1.6.

Matthias

>
> We now have a script to update version numbers; somewhere in the
> devtools I think.
>
> What about to create a new script to list all the code lines with a
> the year number. Then someone can have a look and compare it with the
> current calendar year and if needed create a patch to update all
> affected year numbers at ones.
>
> Maybe a good first step because no year number is forgotten. The next
> one would be to automate this update. But I've not yet an idea how to
> do this.
>
> What do you think?
>
> Marcus
>
>
>
>>> On Oct 20, 2018, at 11:20 AM, Matthias Seidel
>>>  wrote:
>>>
>>> Am 20.10.18 um 17:16 schrieb Jim Jagielski:
 Found it.
>>> Great!

 Fixed in r1844422 and r1844423
>>>
>>> That means, when using --vendor it is updated automatically,
>>> otherwise not?
>>>

> On Oct 20, 2018, at 10:54 AM, Jim Jagielski  wrote:
>
> Are we sure that that part of the splash screen isn't hardcoded in
> (ie: the Copyright part)?
>
> I know that I use '--with-vendor="Apache OpenOffice Community
> Build" \' for macOS and I am guessing the buildbots also use that
> configure option, so maybe that's a clue.
>
>> On Oct 20, 2018, at 9:45 AM, Pedro Lino 
>> wrote:
>>
>> That is probably because your OS is named Darwin (more evolved?) :)
>>
>>
>>
>> 
>>
>>
>>
>>> On October 20, 2018 at 2:35 PM Jim Jagielski 
>>> wrote:
>>>
>>> Hmmm... The macOS builds are showing 2018:
>>>
>>> 
>>>
 On Oct 20, 2018, at 7:14 AM, Pedro Lino <
 pedro.l...@mailbox.org > wrote:

>   But even if I wanted, I can not change the copyright year...
>   That's what I am wondering about. ;-)
>
 Ok. I (wrongly) assumed it was all editable :)


>   BTW: Can you confirm 2017 as copyright year in Jim's Linux
> builds?
>
>
 Yes, Jim's build is showing 2017.


 Regards,

 Pedro
>
>
> -
> 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: Test builds of AOO 4.1.6 HEAD

2018-10-21 Thread Marcus 

Am 20.10.2018 um 20:02 schrieb Jim Jagielski:

That's what it looks like, yeah.


copyright years are always forgotten to update. Every year the same. ;-)

We now have a script to update version numbers; somewhere in the 
devtools I think.


What about to create a new script to list all the code lines with a the 
year number. Then someone can have a look and compare it with the 
current calendar year and if needed create a patch to update all 
affected year numbers at ones.


Maybe a good first step because no year number is forgotten. The next 
one would be to automate this update. But I've not yet an idea how to do 
this.


What do you think?

Marcus




On Oct 20, 2018, at 11:20 AM, Matthias Seidel  
wrote:

Am 20.10.18 um 17:16 schrieb Jim Jagielski:

Found it.

Great!


Fixed in r1844422 and r1844423


That means, when using --vendor it is updated automatically, otherwise not?




On Oct 20, 2018, at 10:54 AM, Jim Jagielski  wrote:

Are we sure that that part of the splash screen isn't hardcoded in (ie: the 
Copyright part)?

I know that I use '--with-vendor="Apache OpenOffice Community Build" \' for 
macOS and I am guessing the buildbots also use that configure option, so maybe that's a 
clue.


On Oct 20, 2018, at 9:45 AM, Pedro Lino  wrote:

That is probably because your OS is named Darwin (more evolved?) :)








On October 20, 2018 at 2:35 PM Jim Jagielski  wrote:

Hmmm... The macOS builds are showing 2018:




On Oct 20, 2018, at 7:14 AM, Pedro Lino < pedro.l...@mailbox.org 
> wrote:


  But even if I wanted, I can not change the copyright year...
  That's what I am wondering about. ;-)


Ok. I (wrongly) assumed it was all editable :)



  BTW: Can you confirm 2017 as copyright year in Jim's Linux builds?



Yes, Jim's build is showing 2017.


Regards,

Pedro



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

Re: Chat Channel (was [Discussion] Program for Sandro)

2018-10-21 Thread sandro 
Dear Gavin,

It was great and worked fine. What time zone do you use?

Glad,
Sandro Suzart



De: Gavin McDonald 
Enviado: domingo, 21 de outubro de 2018 04:37
Para: OOo Apache
Assunto: Re: Chat Channel (was [Discussion] Program for Sandro)

Hi Sandro,

I sent an invite email so that you can join the #openoffice channel, let me
know how it goes.

Gav...


On Sun, Oct 21, 2018 at 3:42 PM sandro  wrote:

> Dear Gavin,
>
> I have followed your instruction. The Slack Site (https://asf.slack.com/)
> says that I need an account to access it. I would like to request one.
>
>
> My greatest motivation for the chat channel is that it will be a facility
> for working everyday. Online with you in real time I plan to work about 2
> hours per day from Monday to Friday and 10 hours in the weekends, it would
> become far easier to my personal management, besides that the possibility
> of collaboration would enhance my productivity and turn me happier and more
> joyful.
>
> Glad,
> Sandro Suzart
>
>
> 
> De: Peter kovacs 
> Enviado: domingo, 14 de outubro de 2018 13:09
> Para: dev@openoffice.apache.org
> Assunto: Re: Chat Channel (was [Discussion] Program for Sandro)
>
> I am online now too.  Thanks Gavin.
>
> Am 14. Oktober 2018 13:21:04 MESZ schrieb Matthias Seidel <
> matthias.sei...@hamburg.de>:
> >Hi Gavin,
> >
> >Am 14.10.2018 um 11:46 schrieb Gavin McDonald:
> >> Install the Slack app, or via the web goto the-asf.slack.com you will
> >find
> >> an #openoffice slack channel ready and waiting, been there quite some
> >time
> >> unused.
> >
> >Thank you for the pointer, I didn't know of it.
> >
> >>
> >> With HipChat going away, Slack is the option to use now.
> >>
> >> I am there, lets see you all there too!
> >
> >I'm in! ;-)
> >
> >Matthias
> >
> >>
> >> HTH
> >>
> >> Gav...
> >>
> >>
> >> On Sun, Oct 14, 2018 at 2:12 AM Howard Cary Morris <
> >> howard_cary_mor...@hotmail.com> wrote:
> >>
> >>> I can create a chat room to share or you can use another service to
> >do the
> >>> same thing
> >>> Howard
> >>>
> >>> From: sandro
> >>> Sent: Friday, October 12, 2018 6:59 PM
> >>> To: dev@openoffice.apache.org
> >>> Subject: Re: Chat Channel (was [Discussion] Program for Sandro)
> >>>
> >>> Hi,
> >>>
> >>> I feel that the chat channel (real time chat) can really improve our
> >>> experience to more creativity, we could be able to communicate and
> >interact
> >>> in real time, certainly our productivity would soar, it would lead
> >us to
> >>> greater satisfaction.
> >>>
> >>> Has anyone felt the same way about that idea? What is your opinion?
> >>>
> >>> When I first gave the idea I was thinking about a communication
> >between me
> >>> and Peter, but as other guys liked that idea then I feel it could be
> >an
> >>> amazing experience to all of us.
> >>>
> >>> Glad,
> >>> Sandro Suzart
> >>>
> >>> 
> >>> De: Peter Kovacs 
> >>> Enviado: segunda-feira, 8 de outubro de 2018 04:11
> >>> Para: dev@openoffice.apache.org
> >>> Assunto: Chat Channel (was [Discussion] Program for Sandro)
> >>>
> >>> Hi all,
> >>>
> >>> I am traveling a lot. The classic irc channel never worked for me,
> >>> because I get disconnects all the time.
> >>>
> >>> So currently from my perspective we could set something up in
> >threema,
> >>> slack or discord for real time chat.
> >>>
> >>> I am also open for other mobile capable options. Just keep in mind
> >it
> >>> has to work with a shitty german mobile connection.
> >>>
> >>> If anyone knows a solution for IRC I would gladly participate in a
> >>> channel there.
> >>>
> >>>
> >>> All the best
> >>>
> >>> Peter
> >>>
> >>> On 9/26/18 3:13 AM, sandro wrote:
>  Dear Peter
> 
>  It is an amazing idea, very nice. Maybe one of those kind services
> >(
> >>> Dropbox or Google) have a nice and amazing chat service so we could
> >>> communicate in real time while working. It is nice to interact and
> >it is
> >>> glad, certainly it will drive us to joy.
>  I would like to try Dropbox and I would like to know if this
> >service has
> >>> means of communication in real time, like a chat?
>  Glad,
>  Sandro Suzart
> 
> 
>  
>  De: Peter Kovacs 
>  Enviado: domingo, 23 de setembro de 2018 12:29
>  Para: dev@openoffice.apache.org
>  Assunto: Re: [Discussion] Program for Sandro
> 
>  Dear Sandro,
> 
>  Glad to read about your determination. :) Lets get you doing
> >something.
> 
>  You can send it directly to my address if you like. I personally
> >would
>  appreciate if we could store it somewhere more cloudy.
> 
>  How about google drive or Dropbox. They offer free cloud space. And
> >you
>  can setup the space easy.
> 
> 
>  Yea it is really cool that we are a cloud Project. I think it is
> >great
>  that

Re: Test builds of AOO 4.1.6 HEAD

2018-10-21 Thread Jim Jagielski 
All uploaded!

> On Oct 20, 2018, at 4:18 PM, Andrea Pescetti  wrote:
> 
> Jim Jagielski wrote:
>> Which langs would people like? I'll upload to my Apache people space.
> 
> Italian please. And thanks to both you and Matthias for providing the builds.
> 
> The Release Candidate will have to be called by Peter, but it looks like we 
> are not far...
> 
> 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: Chat Channel (was [Discussion] Program for Sandro)

2018-10-21 Thread Gavin McDonald 
Hi Sandro,

I sent an invite email so that you can join the #openoffice channel, let me
know how it goes.

Gav...


On Sun, Oct 21, 2018 at 3:42 PM sandro  wrote:

> Dear Gavin,
>
> I have followed your instruction. The Slack Site (https://asf.slack.com/)
> says that I need an account to access it. I would like to request one.
>
>
> My greatest motivation for the chat channel is that it will be a facility
> for working everyday. Online with you in real time I plan to work about 2
> hours per day from Monday to Friday and 10 hours in the weekends, it would
> become far easier to my personal management, besides that the possibility
> of collaboration would enhance my productivity and turn me happier and more
> joyful.
>
> Glad,
> Sandro Suzart
>
>
> 
> De: Peter kovacs 
> Enviado: domingo, 14 de outubro de 2018 13:09
> Para: dev@openoffice.apache.org
> Assunto: Re: Chat Channel (was [Discussion] Program for Sandro)
>
> I am online now too.  Thanks Gavin.
>
> Am 14. Oktober 2018 13:21:04 MESZ schrieb Matthias Seidel <
> matthias.sei...@hamburg.de>:
> >Hi Gavin,
> >
> >Am 14.10.2018 um 11:46 schrieb Gavin McDonald:
> >> Install the Slack app, or via the web goto the-asf.slack.com you will
> >find
> >> an #openoffice slack channel ready and waiting, been there quite some
> >time
> >> unused.
> >
> >Thank you for the pointer, I didn't know of it.
> >
> >>
> >> With HipChat going away, Slack is the option to use now.
> >>
> >> I am there, lets see you all there too!
> >
> >I'm in! ;-)
> >
> >Matthias
> >
> >>
> >> HTH
> >>
> >> Gav...
> >>
> >>
> >> On Sun, Oct 14, 2018 at 2:12 AM Howard Cary Morris <
> >> howard_cary_mor...@hotmail.com> wrote:
> >>
> >>> I can create a chat room to share or you can use another service to
> >do the
> >>> same thing
> >>> Howard
> >>>
> >>> From: sandro
> >>> Sent: Friday, October 12, 2018 6:59 PM
> >>> To: dev@openoffice.apache.org
> >>> Subject: Re: Chat Channel (was [Discussion] Program for Sandro)
> >>>
> >>> Hi,
> >>>
> >>> I feel that the chat channel (real time chat) can really improve our
> >>> experience to more creativity, we could be able to communicate and
> >interact
> >>> in real time, certainly our productivity would soar, it would lead
> >us to
> >>> greater satisfaction.
> >>>
> >>> Has anyone felt the same way about that idea? What is your opinion?
> >>>
> >>> When I first gave the idea I was thinking about a communication
> >between me
> >>> and Peter, but as other guys liked that idea then I feel it could be
> >an
> >>> amazing experience to all of us.
> >>>
> >>> Glad,
> >>> Sandro Suzart
> >>>
> >>> 
> >>> De: Peter Kovacs 
> >>> Enviado: segunda-feira, 8 de outubro de 2018 04:11
> >>> Para: dev@openoffice.apache.org
> >>> Assunto: Chat Channel (was [Discussion] Program for Sandro)
> >>>
> >>> Hi all,
> >>>
> >>> I am traveling a lot. The classic irc channel never worked for me,
> >>> because I get disconnects all the time.
> >>>
> >>> So currently from my perspective we could set something up in
> >threema,
> >>> slack or discord for real time chat.
> >>>
> >>> I am also open for other mobile capable options. Just keep in mind
> >it
> >>> has to work with a shitty german mobile connection.
> >>>
> >>> If anyone knows a solution for IRC I would gladly participate in a
> >>> channel there.
> >>>
> >>>
> >>> All the best
> >>>
> >>> Peter
> >>>
> >>> On 9/26/18 3:13 AM, sandro wrote:
>  Dear Peter
> 
>  It is an amazing idea, very nice. Maybe one of those kind services
> >(
> >>> Dropbox or Google) have a nice and amazing chat service so we could
> >>> communicate in real time while working. It is nice to interact and
> >it is
> >>> glad, certainly it will drive us to joy.
>  I would like to try Dropbox and I would like to know if this
> >service has
> >>> means of communication in real time, like a chat?
>  Glad,
>  Sandro Suzart
> 
> 
>  
>  De: Peter Kovacs 
>  Enviado: domingo, 23 de setembro de 2018 12:29
>  Para: dev@openoffice.apache.org
>  Assunto: Re: [Discussion] Program for Sandro
> 
>  Dear Sandro,
> 
>  Glad to read about your determination. :) Lets get you doing
> >something.
> 
>  You can send it directly to my address if you like. I personally
> >would
>  appreciate if we could store it somewhere more cloudy.
> 
>  How about google drive or Dropbox. They offer free cloud space. And
> >you
>  can setup the space easy.
> 
> 
>  Yea it is really cool that we are a cloud Project. I think it is
> >great
>  that you are with us. Maybe we can make OpenOffice a bit more
> >Cloudy. ;)
> 
>  All the best
> 
>  Peter
> 
>  On 9/22/18 7:32 PM, sandro wrote:
> > Dear Peter,
> >
> > It is always amazing to show my commitment and passion for this
> >>>