I see 4.1.5-dev as a device for testing whether a bug is due to a
specific problem. That change is already checked in to the trunk.
We still have to decide whether to go straight to 4.2.0. The upside is,
as Damjam points out, that we need to get the general benefits of 4.2
out in the field. The downside is that, because of more changes, 4.2.0
has a higher risk of regression. Should 4.2.0 go through field beta-testing?
Going to 4.2.0 would simplify my activities. Because of better debug
building and on general principles, I do my debug and fixing in trunk. I
then have to back port the fixes to the 4.1.x line.
On 11/22/2017 2:37 AM, Damjan Jovanovic wrote:
Thank you, but when are these 4.1.x releases going to stop?
We have so much lined up for 4.2.0.
Damjan
On Mon, Nov 20, 2017 at 5:49 PM, Jim Jagielski <j...@jagunet.com> wrote:
I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
AOO415 branch) available for fun and games (and testing) at:
http://home.apache.org/~jim/AOO-builds/
I've built all langs but have just uploaded: de, en-US, es, fr
and ja (for now). Let me know if people want/need others
uploaded.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
---
This email has been checked for viruses by AVG.
http://www.avg.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
