Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

[Matthias Seidel]

Hi Raphael,

I am not sure if you forgot to write something? ;-)

Matthias


Am 20.05.2017 um 20:52 schrieb Raphael Bircher:
> Am .05.2017, 12:30 Uhr, schrieb Matthias Seidel
> :
>
>> Hi Jim,
>>
>> That is alright with me...
>>
>> ...if we start working on a 4.2.0 branch as soon as possible! ;-)
>>
>> Regards, Matthias
>>
>>
>> Am 17.05.2017 um 17:36 schrieb Jim Jagielski:
>>> My plan is to hold off on accepting this...
>>>
 On May 3, 2017, at 2:36 PM, Marcus  wrote:

 Am 03.05.2017 um 11:54 schrieb Matthias Seidel:
> An installer for Windows (and macOS) with an outdated ASF logo is
> "broken" (in my eyes) ;-)
>
> 80% of our downloads are for Windows, 15% for macOS. They should
> see the
> new logo!
 the logos are visible just at 2 places:
 - splash screen
 --> With the modern PC systems these days it's visible for only -
 hm, let's say - 1,5 sec.

 - About dialog
 --> IMHO a dialog that is one of the most seldom opened dialogs in
 OpenOffice.

 I don't want to sound too negative. I just doubt that the most
 users will notice this graphical change. ;-)

 However, at the end it's the decision of the Release Manager if he
 is accepting this as a blocker.

> Apart from that, no code! Just some graphics...
 Sure, but every change is a risk. And it should be prevented in
 general when it's not necessary. I don't make a difference between
 code and non-code.

 Paranoia? Maybe.
 Experience? Yes.

 Marcus



> Am 03.05.2017 um 00:11 schrieb Marcus:
>> Am 02.05.2017 um 23:51 schrieb Matthias Seidel:
>>> Am 02.05.2017 um 13:42 schrieb Jim Jagielski:
> On Mar 22, 2017, at 8:43 AM, Matthias Seidel
>  wrote:
>
>>> If we decide to get the new ASF logos for the installer, we
>>> should also
>>> update the setup icons for Windows/macOS and the Intro/About
>>> Dialog. But
>>> there has been a discussion with Andrea and Marcus whether to
>>> include
>>> such things or not...
>> correct, new graphics cannot be a blocker for a release. Except the
>> existing ones are broken. But this is not the case here.
>>
>> Sorry, but we should clearly think twice if a change is necessary
>> for
>> a bugfix release. Every change has its own risk.
>>
>> My 2 ct.
>>
>> Marcus

 -
 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.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

[Raphael Bircher]

Am .05.2017, 12:30 Uhr, schrieb Matthias Seidel  
:



Hi Jim,

That is alright with me...

...if we start working on a 4.2.0 branch as soon as possible! ;-)

Regards, Matthias


Am 17.05.2017 um 17:36 schrieb Jim Jagielski:

My plan is to hold off on accepting this...


On May 3, 2017, at 2:36 PM, Marcus  wrote:

Am 03.05.2017 um 11:54 schrieb Matthias Seidel:

An installer for Windows (and macOS) with an outdated ASF logo is
"broken" (in my eyes) ;-)

80% of our downloads are for Windows, 15% for macOS. They should see  
the

new logo!

the logos are visible just at 2 places:
- splash screen
--> With the modern PC systems these days it's visible for only - hm,  
let's say - 1,5 sec.


- About dialog
--> IMHO a dialog that is one of the most seldom opened dialogs in
OpenOffice.

I don't want to sound too negative. I just doubt that the most users  
will notice this graphical change. ;-)


However, at the end it's the decision of the Release Manager if he is  
accepting this as a blocker.



Apart from that, no code! Just some graphics...
Sure, but every change is a risk. And it should be prevented in  
general when it's not necessary. I don't make a difference between  
code and non-code.


Paranoia? Maybe.
Experience? Yes.

Marcus




Am 03.05.2017 um 00:11 schrieb Marcus:

Am 02.05.2017 um 23:51 schrieb Matthias Seidel:

Am 02.05.2017 um 13:42 schrieb Jim Jagielski:

On Mar 22, 2017, at 8:43 AM, Matthias Seidel
 wrote:

If we decide to get the new ASF logos for the installer, we should  
also
update the setup icons for Windows/macOS and the Intro/About  
Dialog. But
there has been a discussion with Andrea and Marcus whether to  
include

such things or not...

correct, new graphics cannot be a blocker for a release. Except the
existing ones are broken. But this is not the case here.

Sorry, but we should clearly think twice if a change is necessary for
a bugfix release. Every change has its own risk.

My 2 ct.

Marcus


-
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








--
My introduction https://youtu.be/Ln4vly5sxYU

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

Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

[Matthias Seidel]

Hi Jim,

That is alright with me...

...if we start working on a 4.2.0 branch as soon as possible! ;-)

Regards, Matthias


Am 17.05.2017 um 17:36 schrieb Jim Jagielski:
> My plan is to hold off on accepting this... 
>
>> On May 3, 2017, at 2:36 PM, Marcus  wrote:
>>
>> Am 03.05.2017 um 11:54 schrieb Matthias Seidel:
>>> An installer for Windows (and macOS) with an outdated ASF logo is
>>> "broken" (in my eyes) ;-)
>>>
>>> 80% of our downloads are for Windows, 15% for macOS. They should see the
>>> new logo!
>> the logos are visible just at 2 places:
>> - splash screen
>> --> With the modern PC systems these days it's visible for only - hm, let's 
>> say - 1,5 sec.
>>
>> - About dialog
>> --> IMHO a dialog that is one of the most seldom opened dialogs in
>> OpenOffice.
>>
>> I don't want to sound too negative. I just doubt that the most users will 
>> notice this graphical change. ;-)
>>
>> However, at the end it's the decision of the Release Manager if he is 
>> accepting this as a blocker.
>>
>>> Apart from that, no code! Just some graphics...
>> Sure, but every change is a risk. And it should be prevented in general when 
>> it's not necessary. I don't make a difference between code and non-code.
>>
>> Paranoia? Maybe.
>> Experience? Yes.
>>
>> Marcus
>>
>>
>>
>>> Am 03.05.2017 um 00:11 schrieb Marcus:
 Am 02.05.2017 um 23:51 schrieb Matthias Seidel:
> Am 02.05.2017 um 13:42 schrieb Jim Jagielski:
>>> On Mar 22, 2017, at 8:43 AM, Matthias Seidel
>>>  wrote:
>>>
> If we decide to get the new ASF logos for the installer, we should also
> update the setup icons for Windows/macOS and the Intro/About Dialog. But
> there has been a discussion with Andrea and Marcus whether to include
> such things or not...
 correct, new graphics cannot be a blocker for a release. Except the
 existing ones are broken. But this is not the case here.

 Sorry, but we should clearly think twice if a change is necessary for
 a bugfix release. Every change has its own risk.

 My 2 ct.

 Marcus
>>
>> -
>> 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.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

[Matthias Seidel]

Just out of curiosity, I built the 4.1.4 branch locally with the updated
graphics for Windows.
First step was en-US and de. Later I will add pt and jp.

As expected there were no building problems, installation went fine and
functionality is normal.

Regards, Matthias

Am 03.05.2017 um 23:17 schrieb Keith N. McKenna:
> On 5/3/2017 2:36 PM, Marcus wrote:
>> Am 03.05.2017 um 11:54 schrieb Matthias Seidel:
>>> An installer for Windows (and macOS) with an outdated ASF logo is
>>> "broken" (in my eyes) ;-)
>>>
>>> 80% of our downloads are for Windows, 15% for macOS. They should see the
>>> new logo!
>> the logos are visible just at 2 places:
>> - splash screen
>> --> With the modern PC systems these days it's visible for only - hm,
>> let's say - 1,5 sec.
>>
>> - About dialog
>> --> IMHO a dialog that is one of the most seldom opened dialogs in
>> OpenOffice.
>>
>> I don't want to sound too negative. I just doubt that the most users
>> will notice this graphical change. ;-)
>>
>> However, at the end it's the decision of the Release Manager if he is
>> accepting this as a blocker.
>>
>>> Apart from that, no code! Just some graphics...
>> Sure, but every change is a risk. And it should be prevented in general
>> when it's not necessary. I don't make a difference between code and
>> non-code.
>>
>> Paranoia? Maybe.
>> Experience? Yes.
>>
>> Marcus
>>
> I have to agree with Marcus on this one. Our Version Number Assignment
> as defined at
> https://cwiki.apache.org/confluence/display/OOOUSERS/Releases is
> ... A release is defined as "only selected
> bug fixes and most often only critical ones. This
> includes any potential security issues."
>
> To me updating a couple of graphics that most users are not going to
> notice anyway does not rise to the threshold of a critical issue. Does
> it need to be done; absolutely. However given the fragility of our build
> system adding another potential failure point to a release that has
> already taken far longer then predicted is a risk that does not need to
> be taken.
>
> Regards
> Keith
>>
>>> Am 03.05.2017 um 00:11 schrieb Marcus:
 Am 02.05.2017 um 23:51 schrieb Matthias Seidel:
> Am 02.05.2017 um 13:42 schrieb Jim Jagielski:
>>> On Mar 22, 2017, at 8:43 AM, Matthias Seidel
>>>  wrote:
>>>
> If we decide to get the new ASF logos for the installer, we should also
> update the setup icons for Windows/macOS and the Intro/About Dialog.
> But
> there has been a discussion with Andrea and Marcus whether to include
> such things or not...
 correct, new graphics cannot be a blocker for a release. Except the
 existing ones are broken. But this is not the case here.

 Sorry, but we should clearly think twice if a change is necessary for
 a bugfix release. Every change has its own risk.

 My 2 ct.

 Marcus
>




smime.p7s
Description: S/MIME Cryptographic Signature

Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

[Matthias Seidel]

OK, let's keep this update small and simple.

I can "patch" those 2 graphics easily myself... ;-)

Matthias


Am 03.05.2017 um 23:17 schrieb Keith N. McKenna:
> On 5/3/2017 2:36 PM, Marcus wrote:
>> Am 03.05.2017 um 11:54 schrieb Matthias Seidel:
>>> An installer for Windows (and macOS) with an outdated ASF logo is
>>> "broken" (in my eyes) ;-)
>>>
>>> 80% of our downloads are for Windows, 15% for macOS. They should see the
>>> new logo!
>> the logos are visible just at 2 places:
>> - splash screen
>> --> With the modern PC systems these days it's visible for only - hm,
>> let's say - 1,5 sec.
>>
>> - About dialog
>> --> IMHO a dialog that is one of the most seldom opened dialogs in
>> OpenOffice.
>>
>> I don't want to sound too negative. I just doubt that the most users
>> will notice this graphical change. ;-)
>>
>> However, at the end it's the decision of the Release Manager if he is
>> accepting this as a blocker.
>>
>>> Apart from that, no code! Just some graphics...
>> Sure, but every change is a risk. And it should be prevented in general
>> when it's not necessary. I don't make a difference between code and
>> non-code.
>>
>> Paranoia? Maybe.
>> Experience? Yes.
>>
>> Marcus
>>
> I have to agree with Marcus on this one. Our Version Number Assignment
> as defined at
> https://cwiki.apache.org/confluence/display/OOOUSERS/Releases is
> ... A release is defined as "only selected
> bug fixes and most often only critical ones. This
> includes any potential security issues."
>
> To me updating a couple of graphics that most users are not going to
> notice anyway does not rise to the threshold of a critical issue. Does
> it need to be done; absolutely. However given the fragility of our build
> system adding another potential failure point to a release that has
> already taken far longer then predicted is a risk that does not need to
> be taken.
>
> Regards
> Keith
>>
>>> Am 03.05.2017 um 00:11 schrieb Marcus:
 Am 02.05.2017 um 23:51 schrieb Matthias Seidel:
> Am 02.05.2017 um 13:42 schrieb Jim Jagielski:
>>> On Mar 22, 2017, at 8:43 AM, Matthias Seidel
>>>  wrote:
>>>
> If we decide to get the new ASF logos for the installer, we should also
> update the setup icons for Windows/macOS and the Intro/About Dialog.
> But
> there has been a discussion with Andrea and Marcus whether to include
> such things or not...
 correct, new graphics cannot be a blocker for a release. Except the
 existing ones are broken. But this is not the case here.

 Sorry, but we should clearly think twice if a change is necessary for
 a bugfix release. Every change has its own risk.

 My 2 ct.

 Marcus
>




smime.p7s
Description: S/MIME Cryptographic Signature

Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

[Keith N. McKenna]

On 5/3/2017 2:36 PM, Marcus wrote:
> Am 03.05.2017 um 11:54 schrieb Matthias Seidel:
>> An installer for Windows (and macOS) with an outdated ASF logo is
>> "broken" (in my eyes) ;-)
>>
>> 80% of our downloads are for Windows, 15% for macOS. They should see the
>> new logo!
> 
> the logos are visible just at 2 places:
> - splash screen
> --> With the modern PC systems these days it's visible for only - hm,
> let's say - 1,5 sec.
> 
> - About dialog
> --> IMHO a dialog that is one of the most seldom opened dialogs in
> OpenOffice.
> 
> I don't want to sound too negative. I just doubt that the most users
> will notice this graphical change. ;-)
> 
> However, at the end it's the decision of the Release Manager if he is
> accepting this as a blocker.
> 
>> Apart from that, no code! Just some graphics...
> 
> Sure, but every change is a risk. And it should be prevented in general
> when it's not necessary. I don't make a difference between code and
> non-code.
> 
> Paranoia? Maybe.
> Experience? Yes.
> 
> Marcus
> 
I have to agree with Marcus on this one. Our Version Number Assignment
as defined at
https://cwiki.apache.org/confluence/display/OOOUSERS/Releases is
... A release is defined as "only selected
bug fixes and most often only critical ones. This
includes any potential security issues."

To me updating a couple of graphics that most users are not going to
notice anyway does not rise to the threshold of a critical issue. Does
it need to be done; absolutely. However given the fragility of our build
system adding another potential failure point to a release that has
already taken far longer then predicted is a risk that does not need to
be taken.

Regards
Keith
> 
> 
>> Am 03.05.2017 um 00:11 schrieb Marcus:
>>> Am 02.05.2017 um 23:51 schrieb Matthias Seidel:
 Am 02.05.2017 um 13:42 schrieb Jim Jagielski:
>> On Mar 22, 2017, at 8:43 AM, Matthias Seidel
>>  wrote:
>>
 If we decide to get the new ASF logos for the installer, we should also
 update the setup icons for Windows/macOS and the Intro/About Dialog.
 But
 there has been a discussion with Andrea and Marcus whether to include
 such things or not...
>>>
>>> correct, new graphics cannot be a blocker for a release. Except the
>>> existing ones are broken. But this is not the case here.
>>>
>>> Sorry, but we should clearly think twice if a change is necessary for
>>> a bugfix release. Every change has its own risk.
>>>
>>> My 2 ct.
>>>
>>> Marcus




signature.asc
Description: OpenPGP digital signature

Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

[Matthias Seidel]

Obviously nobody looks at the splash screen, since the wrong URL has
been there for about 4 years now... ;-)
(When the splash screen was redesigned, the same URL was put in it again)
So I think now it is time for a change and to close this bug.

The ASF logos are also visible during installation on Windows (I can't
verify for macOS, but those graphics have also been updated).
I (and hopefully others) tested the Windows build for several month now.
In fact I am using 4.1.4 on a daily base at work.
For testing the Intro/About I simply copied the new graphics over the
existing ones in OpenOffice/program folder.

So from my POV the risk is minimal to non-existent.

Matthias


Am 03.05.2017 um 20:36 schrieb Marcus:
> Am 03.05.2017 um 11:54 schrieb Matthias Seidel:
>> An installer for Windows (and macOS) with an outdated ASF logo is
>> "broken" (in my eyes) ;-)
>>
>> 80% of our downloads are for Windows, 15% for macOS. They should see the
>> new logo!
>
> the logos are visible just at 2 places:
> - splash screen
> --> With the modern PC systems these days it's visible for only - hm,
> let's say - 1,5 sec.
>
> - About dialog
> --> IMHO a dialog that is one of the most seldom opened dialogs in
> OpenOffice.
>
> I don't want to sound too negative. I just doubt that the most users
> will notice this graphical change. ;-)
>
> However, at the end it's the decision of the Release Manager if he is
> accepting this as a blocker.
>
>> Apart from that, no code! Just some graphics...
>
> Sure, but every change is a risk. And it should be prevented in
> general when it's not necessary. I don't make a difference between
> code and non-code.
>
> Paranoia? Maybe.
> Experience? Yes.
>
> Marcus
>
>
>
>> Am 03.05.2017 um 00:11 schrieb Marcus:
>>> Am 02.05.2017 um 23:51 schrieb Matthias Seidel:
 Am 02.05.2017 um 13:42 schrieb Jim Jagielski:
>> On Mar 22, 2017, at 8:43 AM, Matthias Seidel
>>  wrote:
>>
 If we decide to get the new ASF logos for the installer, we should
 also
 update the setup icons for Windows/macOS and the Intro/About
 Dialog. But
 there has been a discussion with Andrea and Marcus whether to include
 such things or not...
>>>
>>> correct, new graphics cannot be a blocker for a release. Except the
>>> existing ones are broken. But this is not the case here.
>>>
>>> Sorry, but we should clearly think twice if a change is necessary for
>>> a bugfix release. Every change has its own risk.
>>>
>>> My 2 ct.
>>>
>>> Marcus
>
>
> -
> 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.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

[Marcus]

Am 03.05.2017 um 13:45 schrieb Jim Jagielski:

I can't add a Target Milestone of 4.1.4 for BZ issue:

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


strange, it wasn't existing for the "Installation" product but for 
others. I've now added it. Please test if it works for you.


Marcus


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

Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

[Marcus]

Am 03.05.2017 um 11:54 schrieb Matthias Seidel:

An installer for Windows (and macOS) with an outdated ASF logo is
"broken" (in my eyes) ;-)

80% of our downloads are for Windows, 15% for macOS. They should see the
new logo!


the logos are visible just at 2 places:
- splash screen
--> With the modern PC systems these days it's visible for only - hm, 
let's say - 1,5 sec.


- About dialog
--> IMHO a dialog that is one of the most seldom opened dialogs in
OpenOffice.

I don't want to sound too negative. I just doubt that the most users 
will notice this graphical change. ;-)


However, at the end it's the decision of the Release Manager if he is 
accepting this as a blocker.



Apart from that, no code! Just some graphics...


Sure, but every change is a risk. And it should be prevented in general 
when it's not necessary. I don't make a difference between code and 
non-code.


Paranoia? Maybe.
Experience? Yes.

Marcus




Am 03.05.2017 um 00:11 schrieb Marcus:

Am 02.05.2017 um 23:51 schrieb Matthias Seidel:

Am 02.05.2017 um 13:42 schrieb Jim Jagielski:

On Mar 22, 2017, at 8:43 AM, Matthias Seidel
 wrote:


If we decide to get the new ASF logos for the installer, we should also
update the setup icons for Windows/macOS and the Intro/About Dialog. But
there has been a discussion with Andrea and Marcus whether to include
such things or not...


correct, new graphics cannot be a blocker for a release. Except the
existing ones are broken. But this is not the case here.

Sorry, but we should clearly think twice if a change is necessary for
a bugfix release. Every change has its own risk.

My 2 ct.

Marcus



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

Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

[Jim Jagielski]

I can't add a Target Milestone of 4.1.4 for BZ issue:

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

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

Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

[Matthias Seidel]

An installer for Windows (and macOS) with an outdated ASF logo is
"broken" (in my eyes) ;-)

80% of our downloads are for Windows, 15% for macOS. They should see the
new logo!

Apart from that, no code! Just some graphics...

Matthias

Am 03.05.2017 um 00:11 schrieb Marcus:
> Am 02.05.2017 um 23:51 schrieb Matthias Seidel:
>> Am 02.05.2017 um 13:42 schrieb Jim Jagielski:
 On Mar 22, 2017, at 8:43 AM, Matthias Seidel
  wrote:

>> If we decide to get the new ASF logos for the installer, we should also
>> update the setup icons for Windows/macOS and the Intro/About Dialog. But
>> there has been a discussion with Andrea and Marcus whether to include
>> such things or not...
>
> correct, new graphics cannot be a blocker for a release. Except the
> existing ones are broken. But this is not the case here.
>
> Sorry, but we should clearly think twice if a change is necessary for
> a bugfix release. Every change has its own risk.
>
> My 2 ct.
>
> Marcus
>
>
> -
> 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.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

[Marcus]

Am 02.05.2017 um 23:51 schrieb Matthias Seidel:

Am 02.05.2017 um 13:42 schrieb Jim Jagielski:

On Mar 22, 2017, at 8:43 AM, Matthias Seidel  wrote:


If we decide to get the new ASF logos for the installer, we should also
update the setup icons for Windows/macOS and the Intro/About Dialog. But
there has been a discussion with Andrea and Marcus whether to include
such things or not...


correct, new graphics cannot be a blocker for a release. Except the 
existing ones are broken. But this is not the case here.


Sorry, but we should clearly think twice if a change is necessary for a 
bugfix release. Every change has its own risk.


My 2 ct.

Marcus


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

Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

[Matthias Seidel]

Am 02.05.2017 um 13:42 schrieb Jim Jagielski:
>> On Mar 22, 2017, at 8:43 AM, Matthias Seidel  
>> wrote:
>>
>> Hi Raphael,
>>
>> Thank you for your effort!
>> Hopefully Ariel will still be able to assist, but it is really time for a 
>> 4.1.4 RC.
>>
>> May I suggest that these "release blocker" should also be merged:
>>
>> https://bz.apache.org/ooo/show_bug.cgi?id=127253
>> (Update the banners with the new ASF Logo)
> +1: It would be nice to have a complete list of changes required to
> backport from trunk though. Matthias if you want to go ahead and
> handle this, +1 from me.

If we decide to get the new ASF logos for the installer, we should also
update the setup icons for Windows/macOS and the Intro/About Dialog. But
there has been a discussion with Andrea and Marcus whether to include
such things or not...

First all commits for the Windows/macOS installer (including the initial
commit from Raphael):

r1774839
r1782101
r1782134
r1782198
r1782401
r1782502
r1783420
r1783943
r1784016

Now the commits for the setup icons (Windows/macOS):

r1791897
r1792733

Finally the commit for the Intro-Screen/About-Dialog:

r1791815

>> https://bz.apache.org/ooo/show_bug.cgi?id=127176#c24
>> (Java not recognized after update to AOO 4.1.3)
> REOPENED.
>
>> https://bz.apache.org/ooo/show_bug.cgi?id=127341
>> (Update bundled dictionaries for AOO 4.1.4 release)
>>
> +1 as well...
>
>r1784925 r1784961 r1785175 r1793216
>
>
> -
> 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.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

[Andrea Pescetti]

Jim Jagielski wrote:

On May 2, 2017, at 7:42 AM, Jim Jagielski  wrote:

https://bz.apache.org/ooo/show_bug.cgi?id=127341
(Update bundled dictionaries for AOO 4.1.4 release)

+1 as well...
   r1784925 r1784961 r1785175 r1793216

Backported to 4.1.4...


It seems the Bugzilla bot was confused and didn't annotate the issue 
properly in http://svn.apache.org/viewvc?view=revision=1793492


This is a bit of a mess. I've fixed it in the issue page.

Probably, for next commits, you'd better ensure that "#i127341# Updated 
English dictionary" (or equivalent) is the first line of the commit, or 
manually post a comment to the issue as I did.


Note: Ariel is the release manager so the "+" to the blocker should come 
from him. But since he's been unresponsive on the matter, and this is an 
obvious blocker, I felt right to go ahead and use my release manager 
privileges (left from 4.1.2) to mark the issue as a blocker myself.


For other ones like the logo I would suggest a normal process like: the 
issue is nominated as blocker (set to "?"), consensus is built on the 
list and if nobody opposes in the standard 72 hours then someone with 
the right privileges accepts the issue as blocker (set to "+") and then 
code can be backported.


Regards,
  Andrea.

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

Re: Centos5 builds (Was: Re: Release 4.1.3 (4.1.4))

[Andrea Pescetti]

Jim Jagielski wrote:

FWIW, I've kicked off a CentOS5.11 x64 build on my VM.


My CentOS 64 builds are online and confirmed to be working by others who 
use it for daily tasks (see archives of this list, or just ask if you 
need a link). Unless you see a reason for making alternate ones, I think 
Windows would be a wiser investment of time.



I've updated the wiki build page 
(https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step)
with some updates, most due to CentOS5 is now EOL and some urls
have changed. Plus, I needed to manually install File::Path


So this would be

https://wiki.openoffice.org/w/index.php?title=Documentation%2FBuilding_Guide_AOO%2FStep_by_step=237941=237939

The new dependency is strange since I didn't recall needing it, but it 
might have come with some other component in case.


And yes, the fact that CentOS 5 becomes unsupported is the reason for me 
to ask to modify our baseline in future (again, see archives of this 
list); but for sure not for 4.1.4.


Regards,
  Andrea.

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

Re: Centos5 builds (Was: Re: Release 4.1.3 (4.1.4))

[Matthias Seidel]

Am 02.05.2017 um 22:11 schrieb Jim Jagielski:
> Since I'm not doing a Windows build, I assume we don't need to install
> it and have it part of the SVN tag??

I am not so familiar with the procedure, but that sounds reasonable.

So whoever does the Windows builds has to make sure to include
msvcr100.dll, 32bit, version 10.00.40219.325
I think this is the most recent one and use it with AOO 4.1.3 on Windows
for several month.

>
>> On May 2, 2017, at 3:35 PM, Matthias Seidel  
>> wrote:
>>
>> Am 02.05.2017 um 21:17 schrieb Jim Jagielski:
 On May 2, 2017, at 3:01 PM, Matthias Seidel  
 wrote:

 Hi Jim,

 https://bz.apache.org/ooo/show_bug.cgi?id=127176#c24

 We only have to make sure, that we bundle the most recent msvcr100.dll
 (32bit) for the windows build.
 (see: .../main/external/msvcp100/README_msvcX100.dll.txt)
>>> Thx for the info, but I am totally Windows ignorant. When I go
>>> to the link in the BZ page
>>>
>>> https://www.microsoft.com/en-US/download/details.aspx?id=26999
>>>
>>> I get to a MS page where I click download and I get choices for 3 .exe
>>> files, no .dll file.
>>>
>>> According to the BZ page, I should be able to:
>>>
>>>   This should be updated to version 10.0.40219.325 from:
>>> https://www.microsoft.com/en-US/download/details.aspx?id=26999
>>>   for the 4.1.4 Release Candidate.
>>>
>>> So any help here would be appreciated!
>> Yes, one of the 3 files (vcredist_x86.exe) is the runtime for 32bit.
>>
>> I installed it in a VM to get at the dll.
>>
>> I can send you a copy, but it is only used in the Windows builds...
>>
>>
 Regards, Matthias

 P.S.: I will come back later with a full list of commits for the ASF
 logos...

>>> V. Cool. Thx!
>>>
>>>
>>> -
>>> 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: Centos5 builds (Was: Re: Release 4.1.3 (4.1.4))

[Jim Jagielski]

Since I'm not doing a Windows build, I assume we don't need to install
it and have it part of the SVN tag??

> On May 2, 2017, at 3:35 PM, Matthias Seidel  
> wrote:
> 
> Am 02.05.2017 um 21:17 schrieb Jim Jagielski:
>>> On May 2, 2017, at 3:01 PM, Matthias Seidel  
>>> wrote:
>>> 
>>> Hi Jim,
>>> 
>>> https://bz.apache.org/ooo/show_bug.cgi?id=127176#c24
>>> 
>>> We only have to make sure, that we bundle the most recent msvcr100.dll
>>> (32bit) for the windows build.
>>> (see: .../main/external/msvcp100/README_msvcX100.dll.txt)
>> Thx for the info, but I am totally Windows ignorant. When I go
>> to the link in the BZ page
>> 
>>  https://www.microsoft.com/en-US/download/details.aspx?id=26999
>> 
>> I get to a MS page where I click download and I get choices for 3 .exe
>> files, no .dll file.
>> 
>> According to the BZ page, I should be able to:
>> 
>>   This should be updated to version 10.0.40219.325 from:
>> https://www.microsoft.com/en-US/download/details.aspx?id=26999
>>   for the 4.1.4 Release Candidate.
>> 
>> So any help here would be appreciated!
> 
> Yes, one of the 3 files (vcredist_x86.exe) is the runtime for 32bit.
> 
> I installed it in a VM to get at the dll.
> 
> I can send you a copy, but it is only used in the Windows builds...
> 
> 
>> 
>>> Regards, Matthias
>>> 
>>> P.S.: I will come back later with a full list of commits for the ASF
>>> logos...
>>> 
>> V. Cool. Thx!
>> 
>> 
>> -
>> 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: Centos5 builds (Was: Re: Release 4.1.3 (4.1.4))

[Matthias Seidel]

Am 02.05.2017 um 21:17 schrieb Jim Jagielski:
>> On May 2, 2017, at 3:01 PM, Matthias Seidel  
>> wrote:
>>
>> Hi Jim,
>>
>> https://bz.apache.org/ooo/show_bug.cgi?id=127176#c24
>>
>> We only have to make sure, that we bundle the most recent msvcr100.dll
>> (32bit) for the windows build.
>> (see: .../main/external/msvcp100/README_msvcX100.dll.txt)
> Thx for the info, but I am totally Windows ignorant. When I go
> to the link in the BZ page
>
>   https://www.microsoft.com/en-US/download/details.aspx?id=26999
>
> I get to a MS page where I click download and I get choices for 3 .exe
> files, no .dll file.
>
> According to the BZ page, I should be able to:
>
>This should be updated to version 10.0.40219.325 from:
>  https://www.microsoft.com/en-US/download/details.aspx?id=26999
>for the 4.1.4 Release Candidate.
>
> So any help here would be appreciated!

Yes, one of the 3 files (vcredist_x86.exe) is the runtime for 32bit.

I installed it in a VM to get at the dll.

I can send you a copy, but it is only used in the Windows builds...


>
>> Regards, Matthias
>>
>> P.S.: I will come back later with a full list of commits for the ASF
>> logos...
>>
> V. Cool. Thx!
>
>
> -
> 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: Centos5 builds (Was: Re: Release 4.1.3 (4.1.4))

[Jim Jagielski]

> On May 2, 2017, at 3:01 PM, Matthias Seidel  
> wrote:
> 
> Hi Jim,
> 
> https://bz.apache.org/ooo/show_bug.cgi?id=127176#c24
> 
> We only have to make sure, that we bundle the most recent msvcr100.dll
> (32bit) for the windows build.
> (see: .../main/external/msvcp100/README_msvcX100.dll.txt)

Thx for the info, but I am totally Windows ignorant. When I go
to the link in the BZ page

https://www.microsoft.com/en-US/download/details.aspx?id=26999

I get to a MS page where I click download and I get choices for 3 .exe
files, no .dll file.

According to the BZ page, I should be able to:

   This should be updated to version 10.0.40219.325 from:
 https://www.microsoft.com/en-US/download/details.aspx?id=26999
   for the 4.1.4 Release Candidate.

So any help here would be appreciated!

> Regards, Matthias
> 
> P.S.: I will come back later with a full list of commits for the ASF
> logos...
> 

V. Cool. Thx!


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

Re: Centos5 builds (Was: Re: Release 4.1.3 (4.1.4))

[Matthias Seidel]

Hi Jim,

https://bz.apache.org/ooo/show_bug.cgi?id=127176#c24

We only have to make sure, that we bundle the most recent msvcr100.dll
(32bit) for the windows build.
(see: .../main/external/msvcp100/README_msvcX100.dll.txt)

Regards, Matthias

P.S.: I will come back later with a full list of commits for the ASF
logos...


Am 02.05.2017 um 20:40 schrieb Jim Jagielski:
> Went OK... Will now kick off a x32 build...
>
> These are test builds, since we still have 2 backports pending::
>
>> On Mar 22, 2017, at 8:43 AM, Matthias Seidel  
>> wrote:
>>
>> Hi Raphael,
>>
>> Thank you for your effort!
>> Hopefully Ariel will still be able to assist, but it is really time for a 
>> 4.1.4 RC.
>>
>> May I suggest that these "release blocker" should also be merged:
>>
>> https://bz.apache.org/ooo/show_bug.cgi?id=127253
>> (Update the banners with the new ASF Logo)
> +1: It would be nice to have a complete list of changes required to
> backport from trunk though. Matthias if you want to go ahead and
> handle this, +1 from me.
>
>
>> https://bz.apache.org/ooo/show_bug.cgi?id=127176#c24
>> (Java not recognized after update to AOO 4.1.3)
> REOPENED.
>
>
>> On May 2, 2017, at 9:27 AM, Jim Jagielski  wrote:
>>
>> FWIW, I've kicked off a CentOS5.11 x64 build on my VM.
>>
>> I've updated the wiki build page 
>> (https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step)
>> with some updates, most due to CentOS5 is now EOL and some urls
>> have changed. Plus, I needed to manually install File::Path
>> -
>> 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: Centos5 builds (Was: Re: Release 4.1.3 (4.1.4))

[Jim Jagielski]

Went OK... Will now kick off a x32 build...

These are test builds, since we still have 2 backports pending::

> On Mar 22, 2017, at 8:43 AM, Matthias Seidel  
> wrote:
> 
> Hi Raphael,
> 
> Thank you for your effort!
> Hopefully Ariel will still be able to assist, but it is really time for a 
> 4.1.4 RC.
> 
> May I suggest that these "release blocker" should also be merged:
> 
> https://bz.apache.org/ooo/show_bug.cgi?id=127253
> (Update the banners with the new ASF Logo)

+1: It would be nice to have a complete list of changes required to
backport from trunk though. Matthias if you want to go ahead and
handle this, +1 from me.


> 
> https://bz.apache.org/ooo/show_bug.cgi?id=127176#c24
> (Java not recognized after update to AOO 4.1.3)

REOPENED.


> On May 2, 2017, at 9:27 AM, Jim Jagielski  wrote:
> 
> FWIW, I've kicked off a CentOS5.11 x64 build on my VM.
> 
> I've updated the wiki build page 
> (https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step)
> with some updates, most due to CentOS5 is now EOL and some urls
> have changed. Plus, I needed to manually install File::Path
> -
> 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.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

[Jim Jagielski]

> On May 2, 2017, at 7:42 AM, Jim Jagielski  wrote:
> 
>> 
>> https://bz.apache.org/ooo/show_bug.cgi?id=127341
>> (Update bundled dictionaries for AOO 4.1.4 release)
>> 
> 
> +1 as well...
> 
>   r1784925 r1784961 r1785175 r1793216
> 

Backported to 4.1.4...

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

Re: Centos5 builds (Was: Re: Release 4.1.3 (4.1.4))

[Jim Jagielski]

FWIW, I've kicked off a CentOS5.11 x64 build on my VM.

I've updated the wiki build page 
(https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step)
with some updates, most due to CentOS5 is now EOL and some urls
have changed. Plus, I needed to manually install File::Path
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Centos5 builds (Was: Re: Release 4.1.3 (4.1.4))

[Jim Jagielski]

I have 2 CentOS5 VMs setup, one 32bit the other 64. Is anyone else on task
for doing 4.1.4 build for these platforms or should I give it a go?

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

4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

[Jim Jagielski]

> On Mar 22, 2017, at 8:43 AM, Matthias Seidel  
> wrote:
> 
> Hi Raphael,
> 
> Thank you for your effort!
> Hopefully Ariel will still be able to assist, but it is really time for a 
> 4.1.4 RC.
> 
> May I suggest that these "release blocker" should also be merged:
> 
> https://bz.apache.org/ooo/show_bug.cgi?id=127253
> (Update the banners with the new ASF Logo)

+1: It would be nice to have a complete list of changes required to
backport from trunk though. Matthias if you want to go ahead and
handle this, +1 from me.


> 
> https://bz.apache.org/ooo/show_bug.cgi?id=127176#c24
> (Java not recognized after update to AOO 4.1.3)

REOPENED.

> 
> https://bz.apache.org/ooo/show_bug.cgi?id=127341
> (Update bundled dictionaries for AOO 4.1.4 release)
> 

+1 as well...

   r1784925 r1784961 r1785175 r1793216


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

Re: Release 4.1.3 (4.1.4)

[Jim Jagielski]

I've confirmed that except for the '-with-build-version' param, all configure
options and params for 4.1.4 (and, fwiw, 4.1.3) are the same as was done for
4.1.2... I have gone ahead modified '-with-build-version', have committed the
script[1], and will use it.

1. 
http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.4/unxmacos/build_aooreleases.sh?view=log

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

Re: Release 4.1.3 (4.1.4)

[Matthias Seidel]

Am 02.04.2017 um 19:25 schrieb Andrea Pescetti:
> On 20/03/2017 Andrea Pescetti wrote:
>> I think I can provide
>> proper Linux-64 builds from the AOO414 branch matching the 4.1.3
>> specifications (this won't happen before end of March).
>
> I've built the current state of the AOO414 branch (again, this is not
> a Release Candidate) for all languages for the Linux-64 platform. I've
> uploaded a few languages for testing purposes to
>
> https://home.apache.org/~pescetti/openoffice-4.1.4-dev-1781705/
>
> If you'd like to test a language that is not there, just let me know
> and I can upload it. Feedback welcome in general: I mean, the
> differences between 4.1.3 and the uploaded build are so small that
> people who know what they are doing could even install this one and
> use it for day-to-day tasks, for more realistic testing.

Hi Andrea,

Indeed, I downloaded your build (German full installation and en-US
language pack) and use it on a daily base.
No problems on Ubuntu 16.04 64-bit. For me all crashes are gone.

Additionally I use the 4.1.4 version for Windows (from buildbot) for 2
month now without any issues.

Kind regards, Matthias

>
>> I can probably setup a VM for Linux 32-bit too, further in April.
>
> This will need 1-2 more weeks, but the process is fully documented at
>
> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#CentOS_5
>
>
> so anyone can take a look if they wish.
>
> Regards,
>   Andrea.
>
> -
> 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: Release 4.1.3 (4.1.4)

[Andrea Pescetti]

On 20/03/2017 Andrea Pescetti wrote:

I think I can provide
proper Linux-64 builds from the AOO414 branch matching the 4.1.3
specifications (this won't happen before end of March).


I've built the current state of the AOO414 branch (again, this is not a 
Release Candidate) for all languages for the Linux-64 platform. I've 
uploaded a few languages for testing purposes to


https://home.apache.org/~pescetti/openoffice-4.1.4-dev-1781705/

If you'd like to test a language that is not there, just let me know and 
I can upload it. Feedback welcome in general: I mean, the differences 
between 4.1.3 and the uploaded build are so small that people who know 
what they are doing could even install this one and use it for 
day-to-day tasks, for more realistic testing.



I can probably setup a VM for Linux 32-bit too, further in April.


This will need 1-2 more weeks, but the process is fully documented at

https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#CentOS_5

so anyone can take a look if they wish.

Regards,
  Andrea.

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

Re: Release 4.1.3 (4.1.4)

[Matthias Seidel]

Am 02.04.2017 um 14:52 schrieb Andrea Pescetti:
> Matthias Seidel wrote:
>> https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds
>>
>> "The builds linked on this page are intended to be used for *final
>> testing* of release candidates by community volunteers."
>> But the "Buildbot output area" links to a page with snapshots for AOO
>> 4.1.2. Not really helpful...
>
> That's wrong. Well, there is a long story behind this all, but in short:
>
> - Under Apache guidelines, dev builds should not be exposed to the
> generic public, which means that a web page with the builds should not
> be on the openoffice.org domain unless we are sure that people
> understand that these are dev builds only (this also refers to the
> other URL you sent).
>
> - We managed to clarify the above, but still in the meantime we had
> taken the habit to use the wiki page you found as a set of links to
> dev builds.
>
> - In the meantime, the new Infra convention of using the dev space in
> SVN for RCs was instated, and this left us without a "canonical" space
> for the ordinary dev builds - not the buildbots output but builds like
> the ones Jim did and that I am currently doing as a "snapshot" of the
> AOO414 branch.
>
> I'm for deleting all unnecessary pages and resources.

I think the whole documentation needs to be revised.
But I do not have the historical background. ;-)

>
>> At least the Linux Buildbots are working again. Hopefully someone is
>> working on the Windows Buildbots after the migration to Win10/64bit.
>
> Thank you for your work on the Linux bots! And yes, working buildbots
> are not essential for a release but it would be good to see them work
> again.

Mechtilde is pleased to have a German 4.1.4 for Linux. Now she is in
"testing mode" again! ;-)

Regards, Matthias

>
> Regards,
>   Andrea.
>
> -
> 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: Release 4.1.3 (4.1.4)

[Andrea Pescetti]

Matthias Seidel wrote:

https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds
"The builds linked on this page are intended to be used for *final
testing* of release candidates by community volunteers."
But the "Buildbot output area" links to a page with snapshots for AOO
4.1.2. Not really helpful...


That's wrong. Well, there is a long story behind this all, but in short:

- Under Apache guidelines, dev builds should not be exposed to the 
generic public, which means that a web page with the builds should not 
be on the openoffice.org domain unless we are sure that people 
understand that these are dev builds only (this also refers to the other 
URL you sent).


- We managed to clarify the above, but still in the meantime we had 
taken the habit to use the wiki page you found as a set of links to dev 
builds.


- In the meantime, the new Infra convention of using the dev space in 
SVN for RCs was instated, and this left us without a "canonical" space 
for the ordinary dev builds - not the buildbots output but builds like 
the ones Jim did and that I am currently doing as a "snapshot" of the 
AOO414 branch.


I'm for deleting all unnecessary pages and resources.


At least the Linux Buildbots are working again. Hopefully someone is
working on the Windows Buildbots after the migration to Win10/64bit.


Thank you for your work on the Linux bots! And yes, working buildbots 
are not essential for a release but it would be good to see them work again.


Regards,
  Andrea.

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

Re: Release 4.1.3 (4.1.4)

[Matthias Seidel]

Hi Andrea,

Thanks for the clarification!

I found this page:

https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds

"The builds linked on this page are intended to be used for *final
testing* of release candidates by community volunteers."

But the "Buildbot output area" links to a page with snapshots for AOO
4.1.2. Not really helpful...

At least the Linux Buildbots are working again. Hopefully someone is
working on the Windows Buildbots after the migration to Win10/64bit.

Regards, Matthias


Am 01.04.2017 um 00:08 schrieb Andrea Pescetti:
> On 30/03/2017 Matthias Seidel wrote:
>> Unfortunately there is no location for RC described in our cWiki:
>> https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release
>>
>> Definitely a point that should be added...
>
> This is one of the processes where OpenOffice simply behaves as a
> normal Apache project. Release Candidates (please note: ONLY Release
> Candidates) should be uploaded to SVN following the normal process
> outlined at http://www.apache.org/dev/release-publishing.html
>
> This means that Release Candidates for OpenOffice should go here:
> https://dist.apache.org/repos/dist/dev/openoffice/
>
> There are two reasons, though, for us NOT uploading the normal dev
> builds (those that are not meant to be voted upon; of course 4.1.4 is
> not at RC stage) there:
> 1. Uploading dozens of GBytes to SVN is really painful
> 2. Since SVN stores (on the server) the history of all files, this
> would be heavy on the SVN server
>
> So we've traditionally hosted the normal dev builds (before RC) on
> people.apache.org; but Infra decided to replace it with 
> home.apache.org and to make it SFTP-only (no rsync); still, it is
> possible, while still painful, to upload an OpenOffice development
> snapshot there; see
> https://home.apache.org/~pescetti/openoffice-4.1.3-dev-r1761989/binaries/
> as an example.
>
> Which in short means: before RC, use a personal space to share builds,
> home.apache.org being the most "politically correct" option (even
> though from a technical point of view there are no advantages in using
> it rather than a personal web space).
>
> Feel free to include this information in the wiki pages if needed.
>
> Regards,
>   Andrea.
>
> -
> 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: Release 4.1.3 (4.1.4)

[Andrea Pescetti]

On 27/03/2017 Jim Jagielski wrote:

My AOO 4.1.4 builds are ready for upload.


Thanks! I've addressed the "where to upload" question separately. Note: 
these are best defined as AOO414 (this is a name of a branch, not of a 
product) builds since we are still not close to RC stage for OpenOffice 
4.1.4. I think this is clear to everybody, but I repeated it just in 
case someone in the misunderstands these as "possible Release Candidates 
for 4.1.4".



Configure settings were:
LANGS="ast bg ca ca-XR ca-XV cs da de el en-GB en-US es eu fi fr gd gl he hi hu it 
ja kid km ko lt nb nl pl pt pt-BR ru sk sl sr sv ta th tr vi zh-CN zh-TW"
./configure   \
--with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" \
--with-vendor="Apache OpenOffice Community Build" \
--enable-verbose \
--with-openldap \
--enable-category-b \
--enable-bundled-dictionaries \
--enable-wiki-publisher \
--with-junit="/usr/local/share/java/junit.jar" \
--with-jdk-home="$JAVA_HOME" \
--with-ant-home="$ANT_HOME" \
--with-epm=/usr/local/bin/epm \
--with-dmake-path=/usr/local/bin/dmake \
--without-stlport \
--with-package-format="installed dmg" \
--disable-systray \
--with-alloc=system \
--with-lang="${LANGS}"


Where are these settings from?

Here you find the real options used for 4.1.2:

http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.2/unxmacos/build_aooreleases.sh?revision=1736814=markup#l29

While your options seem to follow the script you wrote uploaded to SVN 
for 4.1.3:

http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.3/unxmacos/build_aoo64bit_on_osx10.11.sh?view=log
But if I recall correctly that script was not used for the actual 4.1.3 
builds.


It would be good to use at least the same build version across operating 
systems... but again, this is the reason for having dev builds! So let's 
share what we have, document properly and then fix the differences.


Regards,
  Andrea.

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

Re: Release 4.1.3 (4.1.4)

[Andrea Pescetti]

On 30/03/2017 Matthias Seidel wrote:

Unfortunately there is no location for RC described in our cWiki:
https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release
Definitely a point that should be added...


This is one of the processes where OpenOffice simply behaves as a normal 
Apache project. Release Candidates (please note: ONLY Release 
Candidates) should be uploaded to SVN following the normal process 
outlined at http://www.apache.org/dev/release-publishing.html


This means that Release Candidates for OpenOffice should go here:
https://dist.apache.org/repos/dist/dev/openoffice/

There are two reasons, though, for us NOT uploading the normal dev 
builds (those that are not meant to be voted upon; of course 4.1.4 is 
not at RC stage) there:

1. Uploading dozens of GBytes to SVN is really painful
2. Since SVN stores (on the server) the history of all files, this would 
be heavy on the SVN server


So we've traditionally hosted the normal dev builds (before RC) on 
people.apache.org; but Infra decided to replace it with  home.apache.org 
and to make it SFTP-only (no rsync); still, it is possible, while still 
painful, to upload an OpenOffice development snapshot there; see

https://home.apache.org/~pescetti/openoffice-4.1.3-dev-r1761989/binaries/
as an example.

Which in short means: before RC, use a personal space to share builds, 
home.apache.org being the most "politically correct" option (even though 
from a technical point of view there are no advantages in using it 
rather than a personal web space).


Feel free to include this information in the wiki pages if needed.

Regards,
  Andrea.

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

Re: Release 4.1.3 (4.1.4)

[Matthias Seidel]

Hi Jim,

Unfortunately there is no location for RC described in our cWiki:

https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release

Definitely a point that should be added...

Regards, Matthias

P.S.: Did you also build 4.2.0?


Am 30.03.2017 um 14:54 schrieb Jim Jagielski:
>> On Mar 27, 2017, at 1:17 PM, Jim Jagielski  wrote:
>>
>> My AOO 4.1.4 builds are ready for upload.
>>
> Just need a location to drop 'em off at :)
>
>
> -
> 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: Release 4.1.3 (4.1.4)

[Jim Jagielski]

> On Mar 27, 2017, at 1:17 PM, Jim Jagielski  wrote:
> 
> My AOO 4.1.4 builds are ready for upload.
> 

Just need a location to drop 'em off at :)


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

Re: Release 4.1.3 (4.1.4)

[Jim Jagielski]

My AOO 4.1.4 builds are ready for upload.

Configure settings were:

LANGS="ast bg ca ca-XR ca-XV cs da de el en-GB en-US es eu fi fr gd gl he hi hu 
it ja kid km ko lt nb nl pl pt pt-BR ru sk sl sr sv ta th tr vi zh-CN zh-TW"

./configure   \
--with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" \
--with-vendor="Apache OpenOffice Community Build" \
--enable-verbose \
--with-openldap \
--enable-category-b \
--enable-bundled-dictionaries \
--enable-wiki-publisher \
--with-junit="/usr/local/share/java/junit.jar" \
--with-jdk-home="$JAVA_HOME" \
--with-ant-home="$ANT_HOME" \
--with-epm=/usr/local/bin/epm \
--with-dmake-path=/usr/local/bin/dmake \
--without-stlport \
--with-package-format="installed dmg" \
--disable-systray \
--with-alloc=system \
--with-lang="${LANGS}"
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Release 4.1.3 (4.1.4)

[Matthias Seidel]

Hi Andrea,


Am 24.03.2017 um 01:05 schrieb Andrea Pescetti:
> On 22/03/2017 Matthias Seidel wrote:
>> Hopefully Ariel will still be able to assist, but it is really time for
>> a 4.1.4 RC.
>
> I hope so too, so I would still wait for him as the (currently)
> appointed Release Manager to have the last word on blocker issues.
> This doesn't stop anybody from going on and providing builds.
>
>> May I suggest that these "release blocker" should also be merged:
>> https://bz.apache.org/ooo/show_bug.cgi?id=127253
>> (Update the banners with the new ASF Logo)
>
> This one seems OK (in principle; I haven't looked at the code).

No code, just some updated graphics.
I checked it in the Windows installer, someone else should check it on
macOS.

>
>> https://bz.apache.org/ooo/show_bug.cgi?id=127176#c24
>> (Java not recognized after update to AOO 4.1.3)
>
> This one is marked WONTFIX at
> https://bz.apache.org/ooo/show_bug.cgi?id=127197 - but I don't know if
> there were any relevant code updates.

This is a different bug. Somehow we bundled the msvcr100.dll as 64bit in
4.1.3.
32bit JAVA is not detected with that dll.
I only want to make sure that we bundle the 32bit dll and that it is the
most recent version (10.0.40219.325).

Regards, Matthias

>> https://bz.apache.org/ooo/show_bug.cgi?id=127341
>> (Update bundled dictionaries for AOO 4.1.4 release)
>
> This is a routine check we do before releasing (but still we need an
> issue for that, so thank for creating one!).
>
> Regards,
>   Andrea.
>
> -
> 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: Release 4.1.3 (4.1.4)

[Andrea Pescetti]

On 22/03/2017 Matthias Seidel wrote:

Hopefully Ariel will still be able to assist, but it is really time for
a 4.1.4 RC.


I hope so too, so I would still wait for him as the (currently) 
appointed Release Manager to have the last word on blocker issues. This 
doesn't stop anybody from going on and providing builds.



May I suggest that these "release blocker" should also be merged:
https://bz.apache.org/ooo/show_bug.cgi?id=127253
(Update the banners with the new ASF Logo)


This one seems OK (in principle; I haven't looked at the code).


https://bz.apache.org/ooo/show_bug.cgi?id=127176#c24
(Java not recognized after update to AOO 4.1.3)


This one is marked WONTFIX at 
https://bz.apache.org/ooo/show_bug.cgi?id=127197 - but I don't know if 
there were any relevant code updates.



https://bz.apache.org/ooo/show_bug.cgi?id=127341
(Update bundled dictionaries for AOO 4.1.4 release)


This is a routine check we do before releasing (but still we need an 
issue for that, so thank for creating one!).


Regards,
  Andrea.

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

Re: Release 4.1.3 (4.1.4)

[Raphael Bircher]

Hi Jim, *

That's ok, I think. Andrea told that he would have the builds not befor  
end march. And I'm happy if I have my Windows builds on Monday too.


Regards, Raphael

Am .03.2017, 12:59 Uhr, schrieb Jim Jagielski :


I can have this complete and uploaded by this Monday if that's OK...
I am currently traveling and my AOO build system isn't accessible
from where I am.

On Mar 22, 2017, at 7:52 AM, Jim Jagielski  wrote:


On Mar 21, 2017, at 9:49 AM, Raphael Bircher  
 wrote:



Is there someone who can do Mac OS X?



As mentioned previously, I can. In fact, I have, but it was not
a full-distclean rebuild, so will do again, just to make sure.

Once done, will upload. Suggested upload locations appreciated :)


-
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




--
My introduction https://youtu.be/Ln4vly5sxYU

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

Re: Release 4.1.3 (4.1.4)

[Jim Jagielski]

I can have this complete and uploaded by this Monday if that's OK...
I am currently traveling and my AOO build system isn't accessible
from where I am.
> On Mar 22, 2017, at 7:52 AM, Jim Jagielski  wrote:
> 
> 
>> On Mar 21, 2017, at 9:49 AM, Raphael Bircher  
>> wrote:
>> 
>> 
>> Is there someone who can do Mac OS X?
>> 
> 
> As mentioned previously, I can. In fact, I have, but it was not
> a full-distclean rebuild, so will do again, just to make sure.
> 
> Once done, will upload. Suggested upload locations appreciated :)
> 
> 
> -
> 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: Release 4.1.3 (4.1.4)

[Matthias Seidel]

Hi Raphael,

Thank you for your effort!
Hopefully Ariel will still be able to assist, but it is really time for
a 4.1.4 RC.

May I suggest that these "release blocker" should also be merged:

https://bz.apache.org/ooo/show_bug.cgi?id=127253
(Update the banners with the new ASF Logo)

https://bz.apache.org/ooo/show_bug.cgi?id=127176#c24
(Java not recognized after update to AOO 4.1.3)

https://bz.apache.org/ooo/show_bug.cgi?id=127341
(Update bundled dictionaries for AOO 4.1.4 release)

Kind regards, Matthias


Am 22.03.2017 um 13:01 schrieb Raphael Bircher:
> Hi all
>
> Am .03.2017, 12:52 Uhr, schrieb Jim Jagielski :
>
>>
>>> On Mar 21, 2017, at 9:49 AM, Raphael Bircher
>>>  wrote:
>>>
>>>
>>> Is there someone who can do Mac OS X?
>>>
>>
>> As mentioned previously, I can. In fact, I have, but it was not
>> a full-distclean rebuild, so will do again, just to make sure.
>>
>> Once done, will upload. Suggested upload locations appreciated :)
>>
> Thanks a loat, Jim
>
> Ok, a short summary:
>
> Linux 64 deb/rpm Andrea
> Windows Raphael(I hope I will get it)
> Mac OS X Jim
>
> Regards, Raphael



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Release 4.1.3 (4.1.4)

[Raphael Bircher]

Hi all

Am .03.2017, 12:52 Uhr, schrieb Jim Jagielski :



On Mar 21, 2017, at 9:49 AM, Raphael Bircher   
wrote:



Is there someone who can do Mac OS X?



As mentioned previously, I can. In fact, I have, but it was not
a full-distclean rebuild, so will do again, just to make sure.

Once done, will upload. Suggested upload locations appreciated :)


Thanks a loat, Jim

Ok, a short summary:

Linux 64 deb/rpm Andrea
Windows Raphael(I hope I will get it)
Mac OS X Jim

Regards, Raphael
--
My introduction https://youtu.be/Ln4vly5sxYU

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

Re: Release 4.1.3 (4.1.4)

[Jim Jagielski]

> On Mar 21, 2017, at 9:49 AM, Raphael Bircher  wrote:
> 
> 
> Is there someone who can do Mac OS X?
> 

As mentioned previously, I can. In fact, I have, but it was not
a full-distclean rebuild, so will do again, just to make sure.

Once done, will upload. Suggested upload locations appreciated :)


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

Re: Release 4.1.3 (4.1.4)

[Andrea Pescetti]

Raphael Bircher wrote:

Is there someone who can do Mac OS X?
And Linux 32bit?


Linux 32-bit is not substantially different from the 64-bit case (even 
if it needs to be done on a 32-bit virtual machine). I can probably 
setup a VM for Linux 32-bit too, further in April.


That said, Linux 32-bit is a minority of a minority from our download 
statistics, so this will still leave a significant part of the problem 
unsolved.


Regards,
  Andrea.

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

Re: Release 4.1.3 (4.1.4)

[Raphael Bircher]

Hi all

Am .03.2017, 23:42 Uhr, schrieb Andrea Pescetti :


Raphael Bircher wrote:

@Ariel please give a comment, if you are able to create the Release or
not. If not, I'm willing to volunteer as release manager.


More than a Release Manager we need builds. Can you put builds online  
for people to test? Even though it is (deliberately) complex to do so,  
you can upload them to your home.apache.org account via SFTP.


I can only follow a few discussions lately, but I think I can provide  
proper Linux-64 builds from the AOO414 branch matching the 4.1.3  
specifications (this won't happen before end of March). Unfortunately  
this is only marginally useful as the majority of downloads are for  
other operating systems. So it is very valuable if, on your own machine  
(no buildbots, let's keep it simple), you can provide builds for other  
systems.


Ok, I just started to setup windows for Release compatible builds. But it  
will take some time, since windows is the most nasty platform to build.


Is there someone who can do Mac OS X?

And Linux 32bit?


Regards,
Raphael


--
My introduction https://youtu.be/Ln4vly5sxYU

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

Re: Release 4.1.3 (4.1.4)

[Andrea Pescetti]

Raphael Bircher wrote:

@Ariel please give a comment, if you are able to create the Release or
not. If not, I'm willing to volunteer as release manager.


More than a Release Manager we need builds. Can you put builds online 
for people to test? Even though it is (deliberately) complex to do so, 
you can upload them to your home.apache.org account via SFTP.


I can only follow a few discussions lately, but I think I can provide 
proper Linux-64 builds from the AOO414 branch matching the 4.1.3 
specifications (this won't happen before end of March). Unfortunately 
this is only marginally useful as the majority of downloads are for 
other operating systems. So it is very valuable if, on your own machine 
(no buildbots, let's keep it simple), you can provide builds for other 
systems.


Even 3 languages (English, German and one of your choice) would be 
enough for people to test.


http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/ has some 
information about the environments. But only the Linux one is really clear.


Regards,
  Andrea.

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