RC 3 is announced available by Juergen :
https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds
On Mon, Apr 14, 2014 at 5:51 PM, Edwin Sharp el...@mail-page.com wrote:
Another suggestion:
We should aim for smallest code base.
The smaller the code is, the better chances an update won't break anything.
This can be achieved by:
a. removal of non used features
b. making less used features available via extensions
c. one UI element per task (avoiding duplicates in UI)
d. rewriting certain modules more efficiently (i.e. performing the same
task with 80 lines of code instead 100 lines of code)
On Fri, Apr 11, 2014, at 14:24, Yuzhen Fan wrote:
Hi QAs and all volunteers,
You are invited to test this RC3 if you have time and would like
contribute
to the AOO 4.1.0. Please do testing widely and intensively, from
installation, functions to integration with other applications in your
system.
Any critical problems you find, please report immediately. Thank you!
-- Forwarded message --
From: Jürgen Schmidt jogischm...@gmail.com
Date: Fri, Apr 11, 2014 at 6:57 PM
Subject: [RELEASE]: propose RC3 on revision 1586584
To: dev dev@openoffice.apache.org
Hi,
I would like to propose a new RC3 based on revision 1586584 of our
AOO410 release branch.
Integrated fixes for
https://issues.apache.org/ooo/show_bug.cgi?id=124617
https://issues.apache.org/ooo/show_bug.cgi?id=124639
The fix for https://issues.apache.org/ooo/show_bug.cgi?id=124636 is not
integrated because it is not really critical and the fix is not yet well
enough tested.
It is potentially not understandable for people why we don't integrate
all available fixes but our experience have shown that even minor and on
the first look uncritical fixes can cause regressions. As acting release
manager it is my goal to stabilize the release branch and bring the
planned release out. I am sometimes to optimistic and over motivated and
try to push a release. But this time it becomes again clear that our
code base is tricky and complex and we need probably more time to
stabilize and test it. We published a Beta with 20 downloads and
received no critical feedback which was promising. But with the first RC
we got several critical issues and partly on code that is in the product
since last year. I am sure we can do better and the question after the
release will be how we can improve this. Quality is important for us and
I invite all to think about ways how we can improve this together.
Juergen
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
--
Regards,
Yu Zhen
-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org
--
Regards,
Yu Zhen
