Re: Resigning as RM for 4.1.x

[Dave Fisher]

Hi

Sent from my iPhone

> On Oct 10, 2017, at 2:23 PM, Marcus  wrote:
> 
>> Am 10.10.2017 um 22:56 schrieb Dave Fisher:
>> Hi -
>> Sent from my iPhone
>>> On Oct 10, 2017, at 1:15 PM, Marcus  wrote:
>>> 
>>> Am 10.10.2017 um 22:03 schrieb Jim Jagielski:
> On Oct 10, 2017, at 3:19 PM, Andrea Pescetti  wrote:
> 
> Now the question is, is it OK for us to go ahead, release 4.1.4 with this 
> "known issue" and commit to fixing this and other possible regressions in 
> 4.1.5 next month? Technically, the Release Manager (and I still consider 
> Jim to be in charge, of course!) has the last word. But I'd say everybody 
> is welcome to comment.
 I am 100% fine w/ this. It is a known regression however, but we can
 say that w/ the release of 4.1.4 we are committing ourselves to a 4.1.5 in 
 30-60 days.
>>> 
>>> sounds good.
>> We will need to make sure that people know how to get 4.1.3 if they run into 
>> the issue.
> 
> I think when people can download 4.1.4, then they can also downlaod 4.1.3 to 
> do a downgrade install. Or do you mean to write 1-2 sentences into the 
> release notes?

Yes. A little text about how to downgrade.

Regards,
Dave

> 
>>> Then we can still decide if the amount of issues is high enough to put 
>>> effort into a 4.1.5 release. Or move on to 4.2.0.
>> How stable is trunk?
> 
> I don't remember many tests and reports about these dev builds. So, I would 
> call it: undefined.
> 
> 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

Re: 4.5.0? (Was: Re: AOO 4.2.0 and macOS)

[Patricia Shanahan]

On 10/10/2017 11:49 AM, Marcus wrote:

Am 10.10.2017 um 01:15 schrieb Andrea Pescetti:

Jim Jagielski wrote:

I was wondering... what do people think about going from 4.1.x all the
way straight to 4.5.0...
Since this next "major" release is pretty major, maybe a
bigger step in number might be justified. Especially if
we drop some older supported platforms.


We should focus on 4.1.4 until the release process is complete. And 
then we should start a proper discussion (that I'll be very happy to 
participate in, since my list of pending, realistic, proposals is 
getting longer and longer!) about the next release.


strong +1

To be honest, we have enough to do to get our 4.1.x release out. 
Therefore I doubt we should invest a single minute into the version 
numbering for the next but one release as it is not yet relevant.


my 2 ct.

Marcus


+1

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

Re: Resigning as RM for 4.1.x

[Don Lewis]

On 10 Oct, Rory O'Farrell wrote:
> On Tue, 10 Oct 2017 11:54:54 -0400
> Jim Jagielski  wrote:
> 
>> Have we ever released a X.Y.Za?
> 
> 
> Does it matter? There is a first time for everything.  Why throw all the 
> 4.1.4 work away and start again with 4.1.5?  
> Or call it 4.1.4.1

Figuring out how to do a 4.1.4a or 4.1.4.1 release is probably harder
than adjusting all the knobs to change the release to 4.1.5.


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

Re: 4.1.4 show stopper!

[Don Lewis]

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
the other important and much delayed fixes for other issues.  My
preference would be to release RC4 as-is with an errata notice about
this issue and do a 4.1.5 release as quickly as possible afterwards.

The fact that it took this long for the problem to be identified in the
4.1.4 RC series would seem to indicate that the number of users who
would have to stick with 4.1.3 until 4.1.5 is released would be fairly
small.


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

Re: Resigning as RM for 4.1.x

[Marcus]

Am 10.10.2017 um 22:56 schrieb Dave Fisher:

Hi -

Sent from my iPhone


On Oct 10, 2017, at 1:15 PM, Marcus  wrote:

Am 10.10.2017 um 22:03 schrieb Jim Jagielski:

On Oct 10, 2017, at 3:19 PM, Andrea Pescetti  wrote:

Now the question is, is it OK for us to go ahead, release 4.1.4 with this "known 
issue" and commit to fixing this and other possible regressions in 4.1.5 next month? 
Technically, the Release Manager (and I still consider Jim to be in charge, of course!) 
has the last word. But I'd say everybody is welcome to comment.

I am 100% fine w/ this. It is a known regression however, but we can
say that w/ the release of 4.1.4 we are committing ourselves to a 4.1.5 in 
30-60 days.


sounds good.


We will need to make sure that people know how to get 4.1.3 if they run into 
the issue.


I think when people can download 4.1.4, then they can also downlaod 
4.1.3 to do a downgrade install. Or do you mean to write 1-2 sentences 
into the release notes?



Then we can still decide if the amount of issues is high enough to put effort 
into a 4.1.5 release. Or move on to 4.2.0.


How stable is trunk?


I don't remember many tests and reports about these dev builds. So, I 
would call it: undefined.


Marcus


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

Re: 4.1.4 show stopper!

[Andrea Pescetti]

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 linked sections in many years as 
an OpenOffice users... but we all know that the "important features" are 
different for everybody.



On 10/10/2017 2:59 AM, Mathias Röllig wrote:

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


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).


Regards,
  Andrea.

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

Re: Resigning as RM for 4.1.x

[Dave Fisher]

Hi -

Sent from my iPhone

> On Oct 10, 2017, at 1:15 PM, Marcus  wrote:
> 
> Am 10.10.2017 um 22:03 schrieb Jim Jagielski:
>>> On Oct 10, 2017, at 3:19 PM, Andrea Pescetti  wrote:
>>> 
>>> Now the question is, is it OK for us to go ahead, release 4.1.4 with this 
>>> "known issue" and commit to fixing this and other possible regressions in 
>>> 4.1.5 next month? Technically, the Release Manager (and I still consider 
>>> Jim to be in charge, of course!) has the last word. But I'd say everybody 
>>> is welcome to comment.
>> I am 100% fine w/ this. It is a known regression however, but we can
>> say that w/ the release of 4.1.4 we are committing ourselves to a 4.1.5 in 
>> 30-60 days.
> 
> sounds good.

We will need to make sure that people know how to get 4.1.3 if they run into 
the issue.

> 
> Then we can still decide if the amount of issues is high enough to put effort 
> into a 4.1.5 release. Or move on to 4.2.0.

How stable is trunk?

Regards,
Dave

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

Re: 4.1.4 show stopper!

[Kay Schenk]

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 a "quick fix" I would
> definitely
> > stick to 4.1.4, produce 4.1.4-RC5 and vote on RC5, while undoing
> what we
> > did for 4.1.4-RC4.
> >
>
> +1
>
> > I have
> > still to understand the importance of this bug too - I assume this
> > affects potentially many users, otherwise we can go the slippery way
> of
> > "fix just another small bug" for ages.
> >
>
>
> This is not a fix for a small bug. It is a regression introduced since
> 4.1.3
>
> I believe all regressions from 4.1.3 should be fixed before release. After
> all 4.1.4 is a bug fix release, so regressions are not expected (or
> acceptable IMO)
>
>
> Pedro
>
​
I agree with Pedro's assessment of regressions.



-- 
--
MzK

"Only the truth will save you now."
 -- Ensei Tankado, "Digital Fortress"

Re: Resigning as RM for 4.1.x

[Marcus]

Am 10.10.2017 um 22:03 schrieb Jim Jagielski:



On Oct 10, 2017, at 3:19 PM, Andrea Pescetti  wrote:

Now the question is, is it OK for us to go ahead, release 4.1.4 with this "known 
issue" and commit to fixing this and other possible regressions in 4.1.5 next month? 
Technically, the Release Manager (and I still consider Jim to be in charge, of course!) 
has the last word. But I'd say everybody is welcome to comment.


I am 100% fine w/ this. It is a known regression however, but we can
say that w/ the release of 4.1.4 we are committing ourselves to a 4.1.5 in 
30-60 days.


sounds good.

Then we can still decide if the amount of issues is high enough to put 
effort into a 4.1.5 release. Or move on to 4.2.0.


Marcus


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

Re: Resigning as RM for 4.1.x

[Matthias Seidel]

Am 10.10.2017 um 21:19 schrieb Andrea Pescetti:
> Jim Jagielski wrote:
>> I feel bad leaving RM at this stage... we are so close, and I don't want
>> us to lose momentum. But I also don't want there to be drama
>
> Yes, let's avoid drama, really.
>
> But I'll still send this "modest proposal", based on experience:
>
> 1) We just go ahead and release 4.1.4 as scheduled (i.e., we release
> RC4), at some point within the next 7 days. The "synchronize labels"
> bug becomes a "Known Issue" in the release notes.
>
> 2) Starting today, we incorporate fixes on the AOO415 branch and aim
> at releasing it in, say, early November; AOO415 is only meant to fix
> 4.1.4 regressions and we try to be reasonably strict about this (i.e.,
> we try to avoid the never-ending "just another small fix" syndrome).
>
> 3) We still wait until, say, end of October before producing RCs for
> 4.1.5 since this gives us the time to receive reports of other
> possible bugs/regressions to be fixed in 4.1.5.
>
> Can this work? This covers the case where someone finds a bug the day
> after release; this way we have a window for fixing it in a short term.
>
> My suggestion to keep 4.1.4 was simply pragmatic: those who never
> updated the metadata might believe that 4.1.4->4.1.5 is only a
> one-line change, while the change affects dozens of files and hundreds
> of XML files related to updates and living on another domain. Not
> something that can be done in 10 minutes. Deleting the tag was bad,
> but we never relied on tags: 4.1.3 was tagged several months after it
> was released. To us a release is/was simply the distributed source
> package, not a tag in SVN. But this is a side discussion.
>
> Now the question is, is it OK for us to go ahead, release 4.1.4 with
> this "known issue" and commit to fixing this and other possible
> regressions in 4.1.5 next month? Technically, the Release Manager (and
> I still consider Jim to be in charge, of course!) has the last word.
> But I'd say everybody is welcome to comment.

I think this is a reasonable way...

Another (minor) regression is the Polish dictionary (shame on me!).
Already fixed in trunk and committed to 4.1.5 by Jim.

I may have found another regression, but I need some time to test it and
put it in words...
And then it needs some time fixing it.

So +1 for the timeline.

Matthias

> Regards,
>   Andrea.
>
> -
> 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: Resigning as RM for 4.1.x

[Jim Jagielski]

> On Oct 10, 2017, at 3:19 PM, Andrea Pescetti  wrote:
> 
> Now the question is, is it OK for us to go ahead, release 4.1.4 with this 
> "known issue" and commit to fixing this and other possible regressions in 
> 4.1.5 next month? Technically, the Release Manager (and I still consider Jim 
> to be in charge, of course!) has the last word. But I'd say everybody is 
> welcome to comment.

I am 100% fine w/ this. It is a known regression however, but we can
say that w/ the release of 4.1.4 we are committing ourselves to a 4.1.5 in 
30-60 days.
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Resigning as RM for 4.1.x

[Jim Jagielski]

> On Oct 10, 2017, at 3:19 PM, Andrea Pescetti  wrote:
> 
> To us a release is/was simply the distributed source package, not a tag in 
> SVN. But this is a side discussion.
> 

Agreed. But it is a serious discussion since such policy is NOT part
of the standard release expectations. Their must be a 1-1 match between
released source-code AND a SVN tag (or a specific SVN revision).


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

Re: 4.1.4 show stopper!

[Marcus]

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. 
;-)

Creating the SVN tag must not happen as long as the release is not public on 
servers and communicated to the world.



++1.


I'll fix this in the Wiki.


done in the meantime. Please review:

https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release

Thanks

Marcus




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

Re: 4.1.4 show stopper!

[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. ;-)
> 
> Creating the SVN tag must not happen as long as the release is not public on 
> servers and communicated to the world.
> 

++1.

> I'll fix this in the Wiki.
> 
> Marcus
> 
> 
> 
>>> 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 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 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

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

[Jörg Schmidt]

> 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 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-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Resigning as RM for 4.1.x

[Roberto Galoppini]

2017-10-10 21:19 GMT+02:00 Andrea Pescetti :

> Jim Jagielski wrote:
>
>> I feel bad leaving RM at this stage... we are so close, and I don't want
>> us to lose momentum. But I also don't want there to be drama
>>
>
> Yes, let's avoid drama, really.
>
> But I'll still send this "modest proposal", based on experience:
>
> 1) We just go ahead and release 4.1.4 as scheduled (i.e., we release RC4),
> at some point within the next 7 days. The "synchronize labels" bug becomes
> a "Known Issue" in the release notes.
>
> 2) Starting today, we incorporate fixes on the AOO415 branch and aim at
> releasing it in, say, early November; AOO415 is only meant to fix 4.1.4
> regressions and we try to be reasonably strict about this (i.e., we try to
> avoid the never-ending "just another small fix" syndrome).
>
> 3) We still wait until, say, end of October before producing RCs for 4.1.5
> since this gives us the time to receive reports of other possible
> bugs/regressions to be fixed in 4.1.5.
>
> Can this work? This covers the case where someone finds a bug the day
> after release; this way we have a window for fixing it in a short term.
>

Makes sense to me.
+1

Roberto

>
> My suggestion to keep 4.1.4 was simply pragmatic: those who never updated
> the metadata might believe that 4.1.4->4.1.5 is only a one-line change,
> while the change affects dozens of files and hundreds of XML files related
> to updates and living on another domain. Not something that can be done in
> 10 minutes. Deleting the tag was bad, but we never relied on tags: 4.1.3
> was tagged several months after it was released. To us a release is/was
> simply the distributed source package, not a tag in SVN. But this is a side
> discussion.
>
> Now the question is, is it OK for us to go ahead, release 4.1.4 with this
> "known issue" and commit to fixing this and other possible regressions in
> 4.1.5 next month? Technically, the Release Manager (and I still consider
> Jim to be in charge, of course!) has the last word. But I'd say everybody
> is welcome to comment.
>
> Regards,
>   Andrea.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Re: Resigning as RM for 4.1.x

[Andrea Pescetti]

Jim Jagielski wrote:

I feel bad leaving RM at this stage... we are so close, and I don't want
us to lose momentum. But I also don't want there to be drama


Yes, let's avoid drama, really.

But I'll still send this "modest proposal", based on experience:

1) We just go ahead and release 4.1.4 as scheduled (i.e., we release 
RC4), at some point within the next 7 days. The "synchronize labels" bug 
becomes a "Known Issue" in the release notes.


2) Starting today, we incorporate fixes on the AOO415 branch and aim at 
releasing it in, say, early November; AOO415 is only meant to fix 4.1.4 
regressions and we try to be reasonably strict about this (i.e., we try 
to avoid the never-ending "just another small fix" syndrome).


3) We still wait until, say, end of October before producing RCs for 
4.1.5 since this gives us the time to receive reports of other possible 
bugs/regressions to be fixed in 4.1.5.


Can this work? This covers the case where someone finds a bug the day 
after release; this way we have a window for fixing it in a short term.


My suggestion to keep 4.1.4 was simply pragmatic: those who never 
updated the metadata might believe that 4.1.4->4.1.5 is only a one-line 
change, while the change affects dozens of files and hundreds of XML 
files related to updates and living on another domain. Not something 
that can be done in 10 minutes. Deleting the tag was bad, but we never 
relied on tags: 4.1.3 was tagged several months after it was released. 
To us a release is/was simply the distributed source package, not a tag 
in SVN. But this is a side discussion.


Now the question is, is it OK for us to go ahead, release 4.1.4 with 
this "known issue" and commit to fixing this and other possible 
regressions in 4.1.5 next month? Technically, the Release Manager (and I 
still consider Jim to be in charge, of course!) has the last word. But 
I'd say everybody is welcome to comment.


Regards,
  Andrea.

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

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

[Marcus]

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  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-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: 4.1.4 show stopper!

[Marcus]

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.


I'll fix this in the Wiki.

Marcus




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

Re: 4.1.4 show stopper!

[Marcus]

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 work.

When we look at the history of OpenOffice we haven't released and 
communicated patches for, puh, maybe at least 10 years.


At the end we would put the responsibility to our users to find, 
download, understand and install the patch. I bet that the most of our 
average users will get stuck somewhere in the steps.


Creating an self-extracting and -installing patch for all platforms is 
an enormous effort. Therefore I don't think that we should follow this way.


My 2ct.

Marcus




Am .10.2017, 16:35 Uhr, schrieb Jim Jagielski :


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 that. I will
still produce the required builds. But as long as I'm RM, I can't
abide by "rewriting" history re: 4.1.4... But like I said, I'm OK
w/ someone taking over as RM and will follow their direction
whatever it is.

On Oct 10, 2017, at 9:38 AM, Andrea Pescetti  
wrote:


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 they've never been distributed and they 
can be replaced by new builds.


4.1.4 is tagged but SVN tags can be deleted and recreated. Not best 
practice, but surely feasible.


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 RC5, while 
undoing what we did for 4.1.4-RC4.


Note: I'm writing all of the above without having had the time to 
look at the patch or test. I'll do that this evening, European time. 
I have still to understand the importance of this bug too - I assume 
this affects potentially many users, otherwise we can go the slippery 
way of "fix just another small bug" for ages.


Regards,
 Andrea.



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

Re: We need BZ triage for a 4.1.5 branch...

[Kay Schenk]

On Tue, Oct 10, 2017 at 11:39 AM, Marcus  wrote:

> Am 10.10.2017 um 18:52 schrieb Kay Schenk:
>
>> In light of jimjag's desire to move to 4.1.5 instead of 4.1.4, we need a
>> BZ admin to add 4.1.5 to the release info on:
>>
>> issues.openoffice.org
>>
>
> done
>
> I can help with syncing from 4.1.4 to 4.1.5.
>>
>
> Marcus
>

​Thanks. I will wait a day or so before moving forward with changing things.
​



-- 
--
MzK

"Only the truth will save you now."
 -- Ensei Tankado, "Digital Fortress"

Re: 4.5.0? (Was: Re: AOO 4.2.0 and macOS)

[Marcus]

Am 10.10.2017 um 01:15 schrieb Andrea Pescetti:

Jim Jagielski wrote:

I was wondering... what do people think about going from 4.1.x all the
way straight to 4.5.0...
Since this next "major" release is pretty major, maybe a
bigger step in number might be justified. Especially if
we drop some older supported platforms.


We should focus on 4.1.4 until the release process is complete. And then 
we should start a proper discussion (that I'll be very happy to 
participate in, since my list of pending, realistic, proposals is 
getting longer and longer!) about the next release.


strong +1

To be honest, we have enough to do to get our 4.1.x release out. 
Therefore I doubt we should invest a single minute into the version 
numbering for the next but one release as it is not yet relevant.


my 2 ct.

Marcus


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

Re: Resigning as RM for 4.1.x

[Marcus]

Am 10.10.2017 um 18:01 schrieb Fernando Cassia:

On 10/10/17, Rory O'Farrell  wrote:

On Tue, 10 Oct 2017 11:54:54 -0400
Jim Jagielski  wrote:


Have we ever released a X.Y.Za?



Does it matter? There is a first time for everything.  Why throw all the
4.1.4 work away and start again with 4.1.5?
Or call it 4.1.4.1

Rory


+1


-1

Every version numbering else than x.y.z is not working with our download 
script.


And no, it doesn't make sense to invest hours to adjust it only to 
support this one-time-thing. ;-)


Marcus


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

Re: Resigning as RM for 4.1.x

[Marcus]

Am 10.10.2017 um 19:40 schrieb Peter kovacs:

I support Jim as release manager. I see no big issues, that we can not solve 
together.


I also want that Jim continous as RM.

@Jim:
Please remember that it's allowed to ask for help when you see much work 
and less time on your side. ;-)


Marcus




Am 10. Oktober 2017 19:21:25 MESZ schrieb Patricia Shanahan :

I hope you will stay on. I am not sure I would have made the same
decision as you about the release number, but in my opinion part of the

RM role is bike-shedding prevention by making decisions.

I hope that the need to test the patch ASAP does not get lost in the
discussion of what to call it.



On 10/10/2017 9:50 AM, Jim Jagielski wrote:

I feel bad leaving RM at this stage... we are so close, and I don't

want

us to lose momentum. But I also don't want there to be drama (which
is very, very tiring).

As I said, if I stay on, and am still "picked" as RM, my plan would
be to simply move on to 4.1.5 which is, at this state, the EXACT same
as the AOO414 tag w/ the exception related to the version numbering.

But I want/need feedback from the group if I should stay or if

someone

is willing to take up semi-immediately.



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

Re: We need BZ triage for a 4.1.5 branch...

[Marcus]

Am 10.10.2017 um 18:52 schrieb Kay Schenk:
In light of jimjag's desire to move to 4.1.5 instead of 4.1.4, we need a 
BZ admin to add 4.1.5 to the release info on:


issues.openoffice.org


done


I can help with syncing from 4.1.4 to 4.1.5.


Marcus


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

Re: Resigning as RM for 4.1.x

[Peter kovacs]

I support Jim as release manager. I see no big issues, that we can not solve 
together.

I can take over at 4.1.5, if needed, but not before. I am sorry. Because 
currently I am not up to date about the release and have time restraints until 
20th.

For 4.1.5 we need to communicate, explain the situation. And we should think 
also more about timelines.

All the best
Peter

Am 10. Oktober 2017 19:21:25 MESZ schrieb Patricia Shanahan :
>I hope you will stay on. I am not sure I would have made the same 
>decision as you about the release number, but in my opinion part of the
>
>RM role is bike-shedding prevention by making decisions.
>
>I hope that the need to test the patch ASAP does not get lost in the 
>discussion of what to call it.
>
>
>
>On 10/10/2017 9:50 AM, Jim Jagielski wrote:
>> I feel bad leaving RM at this stage... we are so close, and I don't
>want
>> us to lose momentum. But I also don't want there to be drama (which
>> is very, very tiring).
>> 
>> As I said, if I stay on, and am still "picked" as RM, my plan would
>> be to simply move on to 4.1.5 which is, at this state, the EXACT same
>> as the AOO414 tag w/ the exception related to the version numbering.
>> 
>> But I want/need feedback from the group if I should stay or if
>someone
>> is willing to take up semi-immediately.
>> 
>> -
>> 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

AOO415 branch created

[Jim Jagielski]

https://svn.apache.org/repos/asf/openoffice/branches/AOO415/ 


exists. It was copied directly from AOO414 HEAD which was/is
tags/414

Re: Resigning as RM for 4.1.x

[Patricia Shanahan]

I hope you will stay on. I am not sure I would have made the same 
decision as you about the release number, but in my opinion part of the 
RM role is bike-shedding prevention by making decisions.


I hope that the need to test the patch ASAP does not get lost in the 
discussion of what to call it.




On 10/10/2017 9:50 AM, Jim Jagielski wrote:

I feel bad leaving RM at this stage... we are so close, and I don't want
us to lose momentum. But I also don't want there to be drama (which
is very, very tiring).

As I said, if I stay on, and am still "picked" as RM, my plan would
be to simply move on to 4.1.5 which is, at this state, the EXACT same
as the AOO414 tag w/ the exception related to the version numbering.

But I want/need feedback from the group if I should stay or if someone
is willing to take up semi-immediately.

-
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

We need BZ triage for a 4.1.5 branch...

[Kay Schenk]

In light of jimjag's desire to move to 4.1.5 instead of 4.1.4, we need a 
BZ admin to add 4.1.5 to the release info on:


issues.openoffice.org

I can help with syncing from 4.1.4 to 4.1.5.
--
--
MzK

"Only the truth will save you now."
  -- Ensei Tankado, "Digital Fortress"

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

Re: Resigning as RM for 4.1.x

[Kay Schenk]

Hi all --

It's true that changing from 4.1.4 to 4.1.5 requires a bit of work, but 
really not all that much. It would be better to have Jim continue as RM 
regardless IMO and others can pitch in. Once the branch is copied to 
4.1.5, others can pitch in to do version updates. Non-committers  can 
submit patches toward this endeavor.


I will still help with collecting bugs and resolutions toward this.

On 10/10/2017 09:00 AM, Jim Jagielski wrote:



On Oct 10, 2017, at 11:25 AM, Peter kovacs  wrote:

That's sad news. :(

I have no time until 20th. I would sign up for RM for 4.2.0. (And optional 
4.1.5 if we decide for this approach.)
However I would not do any building only the organisational part of collecting 
bugs and tracking / triggering the advancement.



IMO, it would be better to have someone step up asap... if no one does, or
can, I may be able to move some things around...


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



--
--
MzK

"Only the truth will save you now."
  -- Ensei Tankado, "Digital Fortress"

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

Re: Resigning as RM for 4.1.x

[Jim Jagielski]

I feel bad leaving RM at this stage... we are so close, and I don't want
us to lose momentum. But I also don't want there to be drama (which
is very, very tiring).

As I said, if I stay on, and am still "picked" as RM, my plan would
be to simply move on to 4.1.5 which is, at this state, the EXACT same
as the AOO414 tag w/ the exception related to the version numbering.

But I want/need feedback from the group if I should stay or if someone
is willing to take up semi-immediately.

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

Re: Resigning as RM for 4.1.x

[Matthias Seidel]

Rest assured that I am on standby for the Windows builds!

Whatever version it will be...


Am 10.10.2017 um 17:04 schrieb Jim Jagielski:
> To be honest, I really don't think I have the time or energy at present
> to continue on as RM for the 4.1.x stuff, no matter what we do. After
> being away at confs for ~3weeks, I have quite a bit of a backlog.
>
> Who wants to take over. I still am signing up to do the macOS and
> Linux 32/64 bit builds.
>
> -
> 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: Resigning as RM for 4.1.x

[Jim Jagielski]

> On Oct 10, 2017, at 11:59 AM, Rory O'Farrell  wrote:
> 
> On Tue, 10 Oct 2017 11:54:54 -0400
> Jim Jagielski > wrote:
> 
>> Have we ever released a X.Y.Za?
> 
> 
> Does it matter? There is a first time for everything.  Why throw all the 
> 4.1.4 work away and start again with 4.1.5?  
> Or call it 4.1.4.1
> 

I'm confused. How does calling it 4.1.4.1 or 4.1.4a or even 4.1.4buffalo help?

What exactly does it make easier? We still need to rebuild. And it
doesn't even help w/ the Wiki pages that would need to be renamed.

Re: 4.1.4 RC4: synchronize labels don't work on MacOS

[Matthias Seidel]

+1

Matthias

Am 10.10.2017 um 13:28 schrieb Peter kovacs:
> Can we document the issue in bugzilla?
> Plus maybe link this discussion in it?
>
> Am 10. Oktober 2017 12:54:41 MESZ schrieb Pedro Lino :
>>> 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.
>>
>> I confirm that I can replicate the problem in 4.1.4 RC4 under Windows 7
>> but not when using 4.2.0 (build 1811013)
> -
> 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: Resigning as RM for 4.1.x

[Matthias Seidel]

Either way we would have to update the metadata:

https://bz.apache.org/ooo/show_bug.cgi?id=127168

It would be quite risky to introduce a fourth digit without testing at
this stage...

Matthias


Am 10.10.2017 um 18:01 schrieb Fernando Cassia:
> On 10/10/17, Rory O'Farrell  wrote:
>> On Tue, 10 Oct 2017 11:54:54 -0400
>> Jim Jagielski  wrote:
>>
>>> Have we ever released a X.Y.Za?
>>
>> Does it matter? There is a first time for everything.  Why throw all the
>> 4.1.4 work away and start again with 4.1.5?
>> Or call it 4.1.4.1
>>
>> Rory
> +1
>
> FC
>
> -
> 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: Resigning as RM for 4.1.x

[Fernando Cassia]

On 10/10/17, Rory O'Farrell  wrote:
> On Tue, 10 Oct 2017 11:54:54 -0400
> Jim Jagielski  wrote:
>
>> Have we ever released a X.Y.Za?
>
>
> Does it matter? There is a first time for everything.  Why throw all the
> 4.1.4 work away and start again with 4.1.5?
> Or call it 4.1.4.1
>
> Rory

+1

FC

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

Re: Resigning as RM for 4.1.x

[Jim Jagielski]

> On Oct 10, 2017, at 11:25 AM, Peter kovacs  wrote:
> 
> That's sad news. :(
> 
> I have no time until 20th. I would sign up for RM for 4.2.0. (And optional 
> 4.1.5 if we decide for this approach.)
> However I would not do any building only the organisational part of 
> collecting bugs and tracking / triggering the advancement.
> 

IMO, it would be better to have someone step up asap... if no one does, or
can, I may be able to move some things around...


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

Re: Resigning as RM for 4.1.x

[Rory O'Farrell]

On Tue, 10 Oct 2017 11:54:54 -0400
Jim Jagielski  wrote:

> Have we ever released a X.Y.Za?


Does it matter? There is a first time for everything.  Why throw all the 4.1.4 
work away and start again with 4.1.5?  
Or call it 4.1.4.1

Rory

> 
> > On Oct 10, 2017, at 11:28 AM, Rory O'Farrell  wrote:
> > 
> > On Tue, 10 Oct 2017 17:25:43 +0200
> > Peter kovacs > wrote:
> > 
> >> That's sad news. :(
> >> 
> >> I have no time until 20th. I would sign up for RM for 4.2.0. (And optional 
> >> 4.1.5 if we decide for this approach.)
> >> However I would not do any building only the organisational part of 
> >> collecting bugs and tracking / triggering the advancement.
> >> 
> >> If that's fine for all.
> >> 
> >> One sidenote for all. We need to explain the situation somehow if we do 
> >> not sneak the patch in. ( it seems to be a small thing )
> >> 
> >> All the best
> >> peter
> > 
> > 
> > Put the patch in and call the release 4.1.4a.  Delete existing 4.1.4 
> > versions.
> > 
> > Rory
> > 
> >> 
> >> Am 10. Oktober 2017 17:04:14 MESZ schrieb Jim Jagielski :
> >>> To be honest, I really don't think I have the time or energy at present
> >>> to continue on as RM for the 4.1.x stuff, no matter what we do. After
> >>> being away at confs for ~3weeks, I have quite a bit of a backlog.
> >>> 
> >>> Who wants to take over. I still am signing up to do the macOS and
> >>> Linux 32/64 bit builds.
> >>> 
> >>> -
> >>> 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
> >> 
> >> 
> > 
> > 
> > -- 
> > Rory O'Farrell >
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org 
> > 
> > For additional commands, e-mail: dev-h...@openoffice.apache.org 
> > 


-- 
Rory O'Farrell 

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

Re: 4.1.4 show stopper!

[Jim Jagielski]

> 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
> > 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-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Resigning as RM for 4.1.x

[Jim Jagielski]

Have we ever released a X.Y.Za?

> On Oct 10, 2017, at 11:28 AM, Rory O'Farrell  wrote:
> 
> On Tue, 10 Oct 2017 17:25:43 +0200
> Peter kovacs > wrote:
> 
>> That's sad news. :(
>> 
>> I have no time until 20th. I would sign up for RM for 4.2.0. (And optional 
>> 4.1.5 if we decide for this approach.)
>> However I would not do any building only the organisational part of 
>> collecting bugs and tracking / triggering the advancement.
>> 
>> If that's fine for all.
>> 
>> One sidenote for all. We need to explain the situation somehow if we do not 
>> sneak the patch in. ( it seems to be a small thing )
>> 
>> All the best
>> peter
> 
> 
> Put the patch in and call the release 4.1.4a.  Delete existing 4.1.4 versions.
> 
> Rory
> 
>> 
>> Am 10. Oktober 2017 17:04:14 MESZ schrieb Jim Jagielski :
>>> To be honest, I really don't think I have the time or energy at present
>>> to continue on as RM for the 4.1.x stuff, no matter what we do. After
>>> being away at confs for ~3weeks, I have quite a bit of a backlog.
>>> 
>>> Who wants to take over. I still am signing up to do the macOS and
>>> Linux 32/64 bit builds.
>>> 
>>> -
>>> 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
>> 
>> 
> 
> 
> -- 
> Rory O'Farrell >
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org 
> 
> For additional commands, e-mail: dev-h...@openoffice.apache.org 
> 

Re: Resigning as RM for 4.1.x

[Rory O'Farrell]

On Tue, 10 Oct 2017 17:25:43 +0200
Peter kovacs  wrote:

> That's sad news. :(
> 
> I have no time until 20th. I would sign up for RM for 4.2.0. (And optional 
> 4.1.5 if we decide for this approach.)
> However I would not do any building only the organisational part of 
> collecting bugs and tracking / triggering the advancement.
> 
> If that's fine for all.
> 
> One sidenote for all. We need to explain the situation somehow if we do not 
> sneak the patch in. ( it seems to be a small thing )
> 
> All the best
>  peter


Put the patch in and call the release 4.1.4a.  Delete existing 4.1.4 versions.

Rory

> 
> Am 10. Oktober 2017 17:04:14 MESZ schrieb Jim Jagielski :
> >To be honest, I really don't think I have the time or energy at present
> >to continue on as RM for the 4.1.x stuff, no matter what we do. After
> >being away at confs for ~3weeks, I have quite a bit of a backlog.
> >
> >Who wants to take over. I still am signing up to do the macOS and
> >Linux 32/64 bit builds.
> >
> >-
> >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
> 
> 


-- 
Rory O'Farrell 

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

Re: Resigning as RM for 4.1.x

[Peter kovacs]

That's sad news. :(

I have no time until 20th. I would sign up for RM for 4.2.0. (And optional 
4.1.5 if we decide for this approach.)
However I would not do any building only the organisational part of collecting 
bugs and tracking / triggering the advancement.

If that's fine for all.

One sidenote for all. We need to explain the situation somehow if we do not 
sneak the patch in. ( it seems to be a small thing )

All the best
 peter

Am 10. Oktober 2017 17:04:14 MESZ schrieb Jim Jagielski :
>To be honest, I really don't think I have the time or energy at present
>to continue on as RM for the 4.1.x stuff, no matter what we do. After
>being away at confs for ~3weeks, I have quite a bit of a backlog.
>
>Who wants to take over. I still am signing up to do the macOS and
>Linux 32/64 bit builds.
>
>-
>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

Re: 4.1.4 show stopper!

[Mathias Röllig]

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.


Regards Mathias


Regards Raphael

Am .10.2017, 16:35 Uhr, schrieb Jim Jagielski :


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 that. I will
still produce the required builds. But as long as I'm RM, I can't
abide by "rewriting" history re: 4.1.4... But like I said, I'm OK
w/ someone taking over as RM and will follow their direction
whatever it is.

On Oct 10, 2017, at 9:38 AM, Andrea Pescetti  
wrote:


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 they've never been distributed and they 
can be replaced by new builds.


4.1.4 is tagged but SVN tags can be deleted and recreated. Not best 
practice, but surely feasible.


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 RC5, while 
undoing what we did for 4.1.4-RC4.


Note: I'm writing all of the above without having had the time to 
look at the patch or test. I'll do that this evening, European time. 
I have still to understand the importance of this bug too - I assume 
this affects potentially many users, otherwise we can go the slippery 
way of "fix just another small bug" for ages.


Regards,
 Andrea.

-
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

Re: 4.1.4 show stopper!

[Raphael Bircher]

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


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 that. I will
still produce the required builds. But as long as I'm RM, I can't
abide by "rewriting" history re: 4.1.4... But like I said, I'm OK
w/ someone taking over as RM and will follow their direction
whatever it is.

On Oct 10, 2017, at 9:38 AM, Andrea Pescetti   
wrote:


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 they've never been distributed and they  
can be replaced by new builds.


4.1.4 is tagged but SVN tags can be deleted and recreated. Not best  
practice, but surely feasible.


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 RC5, while  
undoing what we did for 4.1.4-RC4.


Note: I'm writing all of the above without having had the time to look  
at the patch or test. I'll do that this evening, European time. I have  
still to understand the importance of this bug too - I assume this  
affects potentially many users, otherwise we can go the slippery way of  
"fix just another small bug" for ages.


Regards,
 Andrea.

-
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

Resigning as RM for 4.1.x

[Jim Jagielski]

To be honest, I really don't think I have the time or energy at present
to continue on as RM for the 4.1.x stuff, no matter what we do. After
being away at confs for ~3weeks, I have quite a bit of a backlog.

Who wants to take over. I still am signing up to do the macOS and
Linux 32/64 bit builds.

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

Re: 4.1.4 show stopper!

[Jim Jagielski]

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 that. I will
still produce the required builds. But as long as I'm RM, I can't
abide by "rewriting" history re: 4.1.4... But like I said, I'm OK
w/ someone taking over as RM and will follow their direction
whatever it is.

> On Oct 10, 2017, at 9:38 AM, Andrea Pescetti  wrote:
> 
> 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 they've never been distributed and they can be 
> replaced by new builds.
> 
> 4.1.4 is tagged but SVN tags can be deleted and recreated. Not best practice, 
> but surely feasible.
> 
> 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 RC5, while undoing what we did for 
> 4.1.4-RC4.
> 
> Note: I'm writing all of the above without having had the time to look at the 
> patch or test. I'll do that this evening, European time. I have still to 
> understand the importance of this bug too - I assume this affects potentially 
> many users, otherwise we can go the slippery way of "fix just another small 
> bug" for ages.
> 
> Regards,
>  Andrea.
> 
> -
> 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

Re: 4.1.4 show stopper!

[Pedro Lino]

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 RC5, while undoing what we
> did for 4.1.4-RC4.
> 

+1

> I have
> still to understand the importance of this bug too - I assume this
> affects potentially many users, otherwise we can go the slippery way of
> "fix just another small bug" for ages.
> 


This is not a fix for a small bug. It is a regression introduced since 4.1.3

I believe all regressions from 4.1.3 should be fixed before release. After all 
4.1.4 is a bug fix release, so regressions are not expected (or acceptable IMO)


Pedro

Re: 4.1.4 show stopper!

[Raphael Bircher]

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 retiring 4.1.4-RC4 (not 4.1.4 altogether).

Builds are on SourceForge but they've never been distributed and they  
can be replaced by new builds.


4.1.4 is tagged but SVN tags can be deleted and recreated. Not best  
practice, but surely feasible.


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 RC5, while undoing what we  
did for 4.1.4-RC4.


+100



Note: I'm writing all of the above without having had the time to look  
at the patch or test. I'll do that this evening, European time. I have  
still to understand the importance of this bug too - I assume this  
affects potentially many users, otherwise we can go the slippery way of  
"fix just another small bug" for ages.


Regards,
   Andrea.

-
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 show stopper!

[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 retiring 4.1.4-RC4 (not 4.1.4 altogether).

Builds are on SourceForge but they've never been distributed and they 
can be replaced by new builds.


4.1.4 is tagged but SVN tags can be deleted and recreated. Not best 
practice, but surely feasible.


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 RC5, while undoing what we 
did for 4.1.4-RC4.


Note: I'm writing all of the above without having had the time to look 
at the patch or test. I'll do that this evening, European time. I have 
still to understand the importance of this bug too - I assume this 
affects potentially many users, otherwise we can go the slippery way of 
"fix just another small bug" for ages.


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 show stopper!

[Patricia Shanahan]

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 true or false for 
initializing a variable. Unfortunately, I was not able to find any case 
in which it mattered, and used my best judgement based on what I knew at 
the time. It turns out it does matter, and I got it wrong.




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


-
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

Re: 4.1.4 show stopper!

[Jim Jagielski]

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

Re: 4.1.4 show stopper!

[Patricia Shanahan]

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


-
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

Re: 4.1.4 show stopper!

[Jim Jagielski]

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

Re: 4.1.4 show stopper!

[Patricia Shanahan]

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

Index: main/sfx2/source/appl/linkmgr2.cxx
===
--- main/sfx2/source/appl/linkmgr2.cxx  (revision 1811661)
+++ main/sfx2/source/appl/linkmgr2.cxx  (working copy)
@@ -350,7 +350,7 @@
( !bUpdateGrfLinks && OBJECT_CLIENT_GRF == 
pLink->GetObjType() ))
continue;

-   sal_Bool allows = sal_False;
+   sal_Bool allows = sal_True;

if (bAskUpdate)
{

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

Re: 4.1.4 RC4: synchronize labels don't work on MacOS

[Peter kovacs]

Can we document the issue in bugzilla?
Plus maybe link this discussion in it?

Am 10. Oktober 2017 12:54:41 MESZ schrieb Pedro Lino :
>
>> 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.
>> 
>
>
>I confirm that I can replicate the problem in 4.1.4 RC4 under Windows 7
>but not when using 4.2.0 (build 1811013)

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

Re: 4.1.4 RC4: synchronize labels don't work on MacOS

[Pedro Lino]

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


I confirm that I can replicate the problem in 4.1.4 RC4 under Windows 7 but not 
when using 4.2.0 (build 1811013)

Re: 4.1.4 show stopper!

[Patricia Shanahan]

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





-
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

Re: 4.1.4 show stopper!

[Patricia Shanahan]

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

Index: main/sfx2/source/appl/linkmgr2.cxx
===
--- main/sfx2/source/appl/linkmgr2.cxx  (revision 1811661)
+++ main/sfx2/source/appl/linkmgr2.cxx  (working copy)
@@ -350,7 +350,7 @@
( !bUpdateGrfLinks && OBJECT_CLIENT_GRF == 
pLink->GetObjType() ))
continue;

-   sal_Bool allows = sal_False;
+   sal_Bool allows = sal_True;

if (bAskUpdate)
{

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

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

[Mathias Röllig]

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

Re: 4.1.4 RC4: synchronize labels don't work on MacOS

[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

4.1.4 RC4: synchronize labels don't work on MacOS

[FR web forum]

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