issue 127553 (was: 4.1.4 show stopper!)

This is a very good description. Mathias, have you already copied it to Bugzilla? (I've also tested with business cards, but this one looks more generic). Done. https://bz.apache.org/ooo/show_bug.cgi?id=127553 But 4.1.4 isn't available for version in bugzilla. Neither as »Version« nor as

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

As noted, the issue is that AOO414 is tagged. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org

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

Hi all > On October 10, 2017 at 8:47 PM Jörg Schmidt 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

Re: 4.1.4 show stopper!

On 10 Oct, Jim Jagielski wrote: > Thx again! > > Considering this issue, this means that 4.1.4 is also DOA. I will wait for > a few more hours, for West Coast to get online but my plan is to > start the process for AOO-415 Not releasing RC4 will considerably delay releasing a version that has

Re: 4.1.4 show stopper!

Patricia Shanahan wrote: The attached patch fixes this, as well as the business card case. Confirmed. I've just built 4.1.4RC4+patch and the bug was fixed, while 4.1.4RC4 had it. I haven't had the time to check whether this breaks something else yet. To be honest, I don't recall ever using

Re: 4.1.4 show stopper!

On Tue, Oct 10, 2017 at 7:02 AM, Pedro Lino wrote: > Hi Andrea, all > > > Remember that the amount of code changes needed to produce something > > named 4.1.5 is quite significant and very much error-prone. Take a > look > > at the relevant issues in case, but for

Re: 4.1.4 show stopper!

Am 10.10.2017 um 21:54 schrieb Jim Jagielski: On Oct 10, 2017, at 3:05 PM, Marcus wrote: Am 10.10.2017 um 15:12 schrieb Jim Jagielski: The reason is that we have *TAGGED* 4.1.4. :( sad but true, also here we have big bug in our cook book. So, no blame to you. ;-)

Re: 4.1.4 show stopper!

> On Oct 10, 2017, at 3:05 PM, Marcus wrote: > > Am 10.10.2017 um 15:12 schrieb Jim Jagielski: >> The reason is that we have *TAGGED* 4.1.4. :( > > sad but true, also here we have big bug in our cook book. So, no blame to > you. ;-) > > Creating the SVN tag must not

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

> From: Marcus [mailto:marcus.m...@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

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

Re: 4.1.4 show stopper!

Am 10.10.2017 um 15:12 schrieb Jim Jagielski: The reason is that we have *TAGGED* 4.1.4. :( sad but true, also here we have big bug in our cook book. So, no blame to you. ;-) Creating the SVN tag must not happen as long as the release is not public on servers and communicated to the world.

Re: 4.1.4 show stopper!

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. in theory this could

Re: 4.1.4 show stopper!

> On Oct 10, 2017, at 11:19 AM, Mathias Röllig 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 >

Re: 4.1.4 show stopper!

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.

Re: 4.1.4 show stopper!

Hi Jim, * 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. Regards Raphael Am .10.2017, 16:35 Uhr, schrieb Jim

Re: 4.1.4 show stopper!

Once something is tagged it is public. It is official. Removing and/or adjusting tags is something that we cannot and should not do. It is really against ASF policy since it destroys an accurate representation of our history and IP provenance. If someone wishes to take over as RM, I am fine with

Re: 4.1.4 show stopper!

Hi Andrea, all > Remember that the amount of code changes needed to produce something > named 4.1.5 is quite significant and very much error-prone. Take a look > at the relevant issues in case, but for a "quick fix" I would definitely > stick to 4.1.4, produce 4.1.4-RC5 and vote on

Re: 4.1.4 show stopper!

Am .10.2017, 15:38 Uhr, schrieb Andrea Pescetti : Jim Jagielski wrote: Considering this issue, this means that 4.1.4 is also DOA. I will wait for a few more hours, for West Coast to get online but my plan is to start the process for AOO-415 We are still in time for

Re: 4.1.4 show stopper!

Jim Jagielski wrote: Considering this issue, this means that 4.1.4 is also DOA. I will wait for a few more hours, for West Coast to get online but my plan is to start the process for AOO-415 We are still in time for retiring 4.1.4-RC4 (not 4.1.4 altogether). Builds are on SourceForge but

Re: 4.1.4 show stopper!

Don't be confused by my remark about "trunk but with some 4.1.4. changes added". The problem is in the 4.1.4 changes that are in my trunk-based debug environment. Pedro Lino has confirmed that the checked-in trunk does not have the problem. I had a situation in which I had to choose between

Re: 4.1.4 show stopper!

The reason is that we have *TAGGED* 4.1.4. :( > On Oct 10, 2017, at 8:56 AM, Patricia Shanahan wrote: > > Why the need to bump the release number, rather than kill RC4 and build RC5? > > On 10/10/2017 5:54 AM, Jim Jagielski wrote: >> Thx again! >> Considering this issue, this

Re: 4.1.4 show stopper!

Why the need to bump the release number, rather than kill RC4 and build RC5? On 10/10/2017 5:54 AM, Jim Jagielski wrote: Thx again! Considering this issue, this means that 4.1.4 is also DOA. I will wait for a few more hours, for West Coast to get online but my plan is to start the process for

Re: 4.1.4 show stopper!

Thx again! Considering this issue, this means that 4.1.4 is also DOA. I will wait for a few more hours, for West Coast to get online but my plan is to start the process for AOO-415 > On Oct 10, 2017, at 8:16 AM, Patricia Shanahan wrote: > > The attached patch fixes this, as well

Re: 4.1.4 show stopper!

The attached patch fixes this, as well as the business card case. On 10/10/2017 2:59 AM, Mathias Röllig wrote: Hello! Even on Linux. Problem: linked sections will not be updated if the original section is changed. The button [Synchronise Labels] do nothing other than Tools… → Update →

Re: 4.1.4 show stopper!

The equivalent of this patch for my debug environment does fix the labels problem. On 10/10/2017 3:28 AM, Patricia Shanahan wrote: I have a theory for the Labels issue, and am in the process of building to test it. On an extremely experimental, untested, basis I am attaching a candidate

Re: 4.1.4 show stopper!

I have a theory for the Labels issue, and am in the process of building to test it. On an extremely experimental, untested, basis I am attaching a candidate fix. On 10/10/2017 2:59 AM, Mathias Röllig wrote: Hello! Even on Linux. Problem: linked sections will not be updated if the original

4.1.4 show stopper! (was: 4.1.4 RC4: synchronize labels don't work on MacOS)

Hello! Even on Linux. Problem: linked sections will not be updated if the original section is changed. The button [Synchronise Labels] do nothing other than Tools… → Update → Links (or Tools… → Update → Update All). Simply 1. create a new text document 2. insert a section with content 3.