Keep calm and don't over-react Was: Re: 4.1.4 show stopper!

[Marcus <ma...@wtnet.de>]

Reply to all, not only Jim:



Wow, I just had a day off and now my inbox is exploding.

Honestly, was it necessary to act within a few hours? Wouldn't it be 
better to wait more time?

There is no BZ issue, no blocker request, just mails. The builds aren't 
yet public, no communication was gone to the world until now. So, I 
don't see a reason to hurry up here.

Really, please let us follow our own processes. Otherwise we cannot be 
sure not to forget something.

Marcus



Am 10.10.2017 um 17:59 schrieb Jim Jagielski:
> 
>> On Oct 10, 2017, at 11:19 AM, Mathias Röllig <mr...@gmx.net> wrote:
>>
>> Hello Raphael!
>>
>> Am 10.10.2017 um 17:10 schrieb Raphael Bircher:
>>> I understand this, I have just an idea. We keep the 4.1.4 as is and
>>> release a patch for the bug. Then we make just new community builds
>>> with > the patch. Like this we avoid to make a 4.1.5 and we stick
>>> within the ASF policy.
>>
>> A patch for *all* platforms must also be tested in all ways. So I think, this way isn't an easy and good way.
>> Simply let 4.1.4 as is but don't let it (official) free.
>> Create a 4.1.5-RC1 (or maybe 4.1.4-RC5 if possible) with this patch, and if no further errors announce 4.1.5.
>>
> 
> IMO, this does seem like the most prudent way. Yes, it increases *our*
> workload, but it also is the most transparent and prudent for our end-users
> and any ISVs. For better or worse, ASF source code tags are immutable
> since they are the things that "define" a release.


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

Re: Keep calm and don't over-react Was: Re: 4.1.4 show stopper!

[Jim Jagielski <ji...@jaguNET.com>]

As noted, the issue is that AOO414 is tagged.

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

Re: Keep calm and don't over-react Was: Re: 4.1.4 show stopper!

[Pedro Lino <pe...@mailbox.org>]

Hi all

> On October 10, 2017 at 8:47 PM Jörg Schmidt <jo...@j-m-schmidt.de> wrote:

> imho:
> Better to spend more time on a qualitatively good release than to release a less good release overhasty.

+1

> Please don't forget: the quality of AOO is the main argument for many users to choose AOO, especially compared to LO.

+1

> (Yes, bugfixing improves quality, but only if the technical and organizational processes follow the agreed procedures.)

+1

Is the ASF process really so strict that it will force to release 4.1.4 with a known regression? That would be a shot in the foot for AOO. And remember, this is a public mailing list, so the news are already out.

4.1.4 RC4 was never released to the the public. It is Staged in Sourceforge. Is it not possible to go back one step and add the patch to RC5 and still release 4.1.4?

Just my 2 cents.

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

Re: Keep calm and don't over-react Was: Re: 4.1.4 show stopper!

[Jörg Schmidt <jo...@j-m-schmidt.de>]

> From: Marcus [mailto:marcus.mail@wtnet.de] 
> Sent: Tuesday, October 10, 2017 9:17 PM
> To: dev@openoffice.apache.org
> Subject: Keep calm and don't over-react Was: Re: 4.1.4 show stopper!
> 
> Reply to all, not only Jim:
> 
> 
> 
> Wow, I just had a day off and now my inbox is exploding.
> 
> Honestly, was it necessary to act within a few hours? Wouldn't it be 
> better to wait more time?
> 
> There is no BZ issue, no blocker request, just mails. The 
> builds aren't 
> yet public, no communication was gone to the world until now. So, I 
> don't see a reason to hurry up here.
> 
> Really, please let us follow our own processes. Otherwise we 
> cannot be 
> sure not to forget something.
> 
> Marcus


I support what Marcus has said.

imho:
Better to spend more time on a qualitatively good release than to release a less good release overhasty.

Please don't forget: the quality of AOO is the main argument for many users to choose AOO, especially compared to LO.
(Yes, bugfixing improves quality, but only if the technical and organizational processes follow the agreed procedures.)



greetings.
Jörg


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