incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Weir <>
Subject Re: [RELEASE][3.4.1]: propose new snapshot based on revision 1372282
Date Tue, 14 Aug 2012 22:02:35 GMT
On Mon, Aug 13, 2012 at 4:27 AM, J├╝rgen Schmidt
<> wrote:
> Hi,
> after a short break I have checked the current situation and where we are.
> We had identified some further issues for 3.4.1 while we continued
> testing the latest snapshots. These issues are now fixed and I would
> like to propose a new snapshot build based on revision 1372282.
> Issues that will be fixed in this new snapshot:
> - OO crashes when I Print
> - Remove the "Browser Plug-in" tab page from the Options dialog
> - Starting OpenOffice with "-nodefault" parameter should not open the
> StartCenter
> The last 2 issues matched not directly our criteria for blocker issues
> but after reviewing the issues and the fix I decided to integrate them
> in 3.4.1 as well.
> The reason for integrating the last issue is quite simple and I believe
> that we probably share this view. We want that AOO is used in
> combination with other software systems and as backend service for
> document conversion etc. From my point of view it make sense to
> integrate this fix in 3.4.1.

Here's what I see in '282.  It is good so far.

I tested 6 different VM's with the following scenarios, all 32-bit:

- Fresh install on XP
- Fresh  install on Windows 8
- Fresh install on Windows 9 Preview

- Install over OOo 3.3.0 on XP
- Install over AOO 3.4.0 on XP
- Install co-existing with LO 3.6.0 on XP

I didn't do heavy testing, but verified the basic operations, and
verified some of the release blocker fixes.

I'll continue doing informal testing of the above.

No problems so far, except for Windows 8, where the lack of a digital
signatures leads to a very poor user experience.  In the default
configuration, downloading with I.E and installing will cause Windows
to warn the user 3 separate times, with a scary message about how the
software might harm their system.  In one case the UI makes it look
like the user cannot install at all.  They need to expand a collapsed
section in the dialog to see the "install anyways" option.

I realize there is nothing we can at this point, but we should try
help the users deal with this as much as we can.  I'll try repeating
this to get some screen shots we can use to explain this.

I did one further VM, with Kaspersky antivirus, with latest signatures
to verify the installer and installed image.  We should probably do
that on Mac as well, just to make sure nothing sneaked in to our build
machines.  Any volunteers?


> Juergen

View raw message