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: 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