Re: [DISCUSS] Release 4.2: General Topics

[Andrea Pescetti]

On 24/08/2016 Don Lewis wrote:

   * Updated bundled serf to fix a CVE and a WebDAV issue.  The FreeBSD
 port has been using the system version of the latest and greatest.


We've been discussing this separately. This will make the build system 
even more complex, but it does have advantages and brings to completion 
work started with 4.1.2.



   * Handle the Wiki Publisher and PDF Import extensions as integrated
 extensions:
 
 I've done some work on this in the FreeBSD port, but I haven't
 tackled the installer part for other platforms.


Can you elaborate on this? For example the fact that they shouldn't ping 
for updates looks problematic (not so bad, but it will require a 
reasonable release pace). And actually the document suggests that 
bundled dictionaries are handled as integrated extensions, which is not 
the case at the moment - and this allows users to get, for example, a 
fresh English dictionary when they wish.



Someone should fix the broken spellcheck problem.  It generates a lot of
complaints from our users.


We've investigated it a length; it is uncommon (it seems common due to 
the huge number of users) and like Rory and Dennis wrote this is better 
fixed with an after-the-fact fix: a tool (which ideally would become a 
menu item or a first start option) that allows to start with a clean 
profile.


Regards,
  Andrea.

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

Re: [DISCUSS] Release 4.2: General Topics

[Andrea Pescetti]

Resending to 3 lists... I suggest to have a "canonical" reply-to to the 
dev list for the next messages. Andrea


Andrea Pescetti wrote:

On 23/08/2016 Kay Schenk wrote:

WARNING: This is quite long!


And the discussion was even longer, but I'll start with answering this one.

And I'll first note that:

1) Work is not starting now. We have years of code already committed and
not shown in previous releases.

2) Like for every release, we make plans but at a certain point we have
to cut the release and this "wishlist" is thus a tentative guideline.


*PRIORITIES*
1. Update the localization.
We've had quite a bit of work by the localization folks since the 4.1.1
release. This was the last release, in 2014-08-21 to import localization
updates. Currently, it seems we might also add 3 new languages: Uyghur,
Sinhala, and Icelandic with the 4.2 release. This would include both UI
translations and Help translations.


Last translations import were done in 4.1.0 and not 4.1.1 (if I recall
correctly); but this is a minor detail. There are no new languages to be
expected in 4.2.0: we have new languages in Pootle, but I don't think
any of them is ready enough for being released (this may of course
improve with time). So in short 4.2.0 means that we can add strings to
the code, which means we can make them available to translators, which
in turn means we can (we have to) update all translations.


We need volunteers to lead this endeavor. I, personally, don't know
anything about this process.


I'm slowly working on this but I still have something to find/learn.
I've sent the l10n list a mail sending that I'm planning to test a first
import in early September - just to test the process.


2. Update Java requirement from Java 1.5 to *at least* Java 1.7
I am rather adamant that we change our building requirement to Java 1.7
for all platforms. I will be changing that in our Building Guide today.


Is there a real reason for it? I see this like saying (this is just an
example, not to be taken literally) "we drop support for Windows XP
since it's old and unsupported". In short: if we need work to drop Java
1.5 then we have clear advantages in raising our requirement to 1.7,
otherwise we can simply drop the requirement saying "we won't explicitly
test compatibility with Java < 1.7"; but in that case we must provide
ways to obtain a compatible JRE for all the 4 supported platforms.


3. Issues for inclusion
We need to include submitted/tested patches since 4.0.x. This should not
include UI changes which would need to undergo a much longer test period.


The version number is not a detail. We call it 4.2.0 since UI changes
are allowed. On the other hand, we don't have to include all patches;
actually, seeing all the code that already went in, I would be more on
the conservative side here.


Additionally, issue 127068, involving analytics on our source code would
surely be worth investigating.
https://bz.apache.org/ooo/show_bug.cgi?id=127068


These are automatically found defects, good for easy fixes but probably
not really important.

I'd rather suggest that we give some attention to the 4.1.2 regressions,
especially this one (the only one so far):
https://bz.apache.org/ooo/show_bug.cgi?id=126622


*BUILDBOTS AND CONFIGURATION*
1. Move to different buildbots?


Not needed. A "nice to have" if they standardize it, but buildbots (I
mean, the Linux version they use) are not so relevant for a release.


2. Configuration Issues
Add, at least the ant version we're checking for in our configuration is
not the version recommended in our Building Guide.


The this is a bug in configure, needs its own issue and must be checked.


*PRODUCTION ENVIRONMENT* ...
It has
been suggested that we use the ASF buildbots to produce our binaries
with this release.


The ASF buildbots and releases cover two different fields. I've been
misunderstood from time to time, but just to make it clear: I would
never want that we use the buildbots for releasing (at least for Linux),
since you want a recent Linux on buildbots and on old Linux on the
release VM (where this VM is hosted can be deferred to a separate thread).


Andrea has volunteered to set up a production environment for us. SEE:
http://markmail.org/message/b4dbjdeu4llczqwt


I see that discussion has been misunderstood. I'll reply there. It
suffices to say, here, that I'm not suggesting to use buildbots for the
release builds. Which basically means I agree with your point of view in
this respect.

Regards,
   Andrea.

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




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

Re: [DISCUSS] Release 4.2: General Topics

[Don Lewis]

Here is my list:

  * Update bundled redland / rasqal / raptor to fix a CVE.  This is
currently in progress.  The FreeBSD port has been using the system
versions of the latest and greatest.

  * Updated bundled serf to fix a CVE and a WebDAV issue.  The FreeBSD
port has been using the system version of the latest and greatest.

  * [low priority] Update bundled vigra.  This version is no longer
available upstream.  It is used by the basebmp module, but I don't
know what it is used for or how to test it.  I believe only the
headers are used.  The FreeBSD port uses the latest and greatest
version and I haven't heard of any problems.

  * [low priority] Updated bundled CoinMP.  There has been an API
change, which prevents the FreeBSD port from using the system
version.  Difficulty unknown ...

  * Fix the easy to fix compiler warnings.  In the case of unused
private class member variables, deleting them would cause an ABI
change because the object size would shrink.  If that is a problem
the alternate would be to mark them unused.  I think there are only
a small number of these, but they get reported many times.

  * Handle the Wiki Publisher and PDF Import extensions as integrated
extensions:

I've done some work on this in the FreeBSD port, but I haven't
tackled the installer part for other platforms.

  * Fix a problem that I stumbled across involving extensions that can
cause an infinite crash / recover loop.  I think I can generate an
alert when I detect the problem.  I'm not sure if I can use an
existing alert message or will need a new one.  If the latter, then
there will be some translation work required.

  * Give network connection failures a more informative error message.
I stumbled across this when tracking down a problem that was
confined to FreeBSD.


Someone should fix the broken spellcheck problem.  It generates a lot of
complaints from our users.


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