openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthias Seidel <matthias.sei...@hamburg.de>
Subject Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))
Date Mon, 15 May 2017 16:28:48 GMT
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
> <major>.<minor>.<micro>. A <micro>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
>>>>>>> <matthias.seidel@hamburg.de> 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
>



Mime
View raw message