The reason is that we have *TAGGED* 4.1.4. :(

> On Oct 10, 2017, at 8:56 AM, Patricia Shanahan <p...@acm.org> 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 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 <p...@acm.org> wrote:
>>> 
>>> 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 → 
>>>> Links (or Tools… → Update → Update All).
>>>> Simply
>>>> 1. create a new text document
>>>> 2. insert a section with content
>>>> 3. insert a section as link to the first section
>>>> 4. change the content of the first section
>>>> 5. Tools… → Update → Links
>>>> or Tools… → Update → Update All
>>>> => Nothing happens. :-(
>>>> Regards, Mathias
>>>> Am 10.10.2017 um 11:10 schrieb Patricia Shanahan:
>>>>> Thanks for the report.
>>>>> 
>>>>> I have reproduced the problem in my Windows 8.1 debug environment, based 
>>>>> on trunk but with some 4.1.4 changes added. I need to get some more sleep 
>>>>> before serious debug (it is 2:08 a.m. here). Could someone check whether 
>>>>> it happens in the unmodified trunk? That would narrow it down.
>>>>> 
>>>>> On 10/10/2017 12:49 AM, FR web forum wrote:
>>>>>> Hello dev,
>>>>>> FYI a french user reports this on MacBook Pro SSD OS X 10.12.6 Sierra
>>>>>> Run File - New - Business Cards
>>>>>> Choose how your business cards will look
>>>>>> Click on New document
>>>>>> Modifiy the first label
>>>>>> When you click on the Synchronize Labels button, the current label is 
>>>>>> not copied to all others.
>>>>>> 
>>>>>> Rollback to 4.1.3: works as expected.
>>>>>> 
>>>>>> ---------------------------------------------------------------------
>>>>>> 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
>>>>> 
>>>>> 
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>> <labels_bug.patch>
>>> ---------------------------------------------------------------------
>>> 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
> 
> ---------------------------------------------------------------------
> 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

Reply via email to