You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Andrea Pescetti <pe...@apache.org> on 2015/07/12 15:57:53 UTC
[RELEASE] Contents of OpenOffice 4.1.2
It's time to decide what goes into 4.1.2 and what doesn't. Not in terms
of specific bugfixes (we have the standard process of nominating release
blockers for this and I don't plan to change it), but in terms of
categories. The following is a realistic list of what we can have in
4.1.2. Shall we take it as the overall plan for 4.1.2?
1. Bugfixes
This is obvious: being a bugfix release, OpenOffice 4.1.2 will contain
fixes for the most important/annoying 4.1.1 bugs. Actually 4.1.1 is
proving to be very stable, but we have some bugs fixed on trunk already
(and a few more with patches ready) that should be considered. We'll
come to this in separate discussions.
2. Features
As the release number tells, OpenOffice 4.1.2 is not meant to come with
many new features. But there are two fields where we should make
exceptions and introduce new features:
* Digital signing: Infra has prepared months ago (with significant
investments) the whole infrastructure for us to produce digitally signed
packages, which would install with no problems/warnings for Windows
users. Jan already made some experiments, but he also clarified he will
be very busy with organizing ApacheCon in these months, so we may need
someone to step up here.
* Windows 10: Millions of our users will run Windows 10 within a few
weeks. OpenOffice is reported to work smoothly on Windows 10
pre-releases. Should any major Windows 10 incompatibilities appear, they
should be fixed in 4.1.2.
3. Localization
* Existing translations: Pootle is now tracking the 4.2.0 release, so
translators do not have an immediate way to fix translations for 4.1.2.
There is a possibility to check whether we can reuse the 4.2.0 strings
for 4.1.2, but due to the version clash I would prefer to fix strings
upon request, in the SDF files directly and only in the case of major,
well-defined bugs (example: the Italian version has a typo in a main
menu item; it is fixed in Pootle for 4.2.0 AND we can edit the SDF file
manually to fix it for the 4.1.x line).
* New translations: same problem with Pootle; we don't have any new
translations (additional with respect to 4.1.1) ready at the moment; if
a translation reaches 100%, I'm available to investigate better what we
can do with the Pootle 4.2.0 strings for 4.1.2, since that would be the
most logical solution.
* Existing dictionaries: no problem, we will integrate them as usual. A
deadline will be agreed upon and sent to the l10n list.
* New dictionaries: no problem, we will integrate them as usual. A
deadline will be agreed upon and sent to the l10n list.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE] Contents of OpenOffice 4.1.2
Posted by Andrea Pescetti <pe...@apache.org>.
On 19/07/2015 Andrea Pescetti wrote:
> On 12/07/2015 Andrea Pescetti wrote:
>> * Existing dictionaries: no problem, we will integrate them as usual. A
>> deadline will be agreed upon and sent to the l10n list.
>> * New dictionaries: no problem, we will integrate them as usual. A
>> deadline will be agreed upon and sent to the l10n list.
> We keep dictionaries pending, waiting for the Extensions site to be
> fully available again
The Extensions site has come back to normal operation for a few weeks,
so I now propose, subject to lazy consensus, 16 August as a deadline for
suggesting new/updated dictionaries. Later additions can be considered
depending on other activities, but updates requested by 16 August are
guaranteed to appear in 4.1.2.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE] Contents of OpenOffice 4.1.2
Posted by Andrea Pescetti <pe...@apache.org>.
On 12/07/2015 Andrea Pescetti wrote:
> It's time to decide what goes into 4.1.2 and what doesn't.
Thanks for the feedback (some of it will be addressed in separate
threads). I'm coming back to this discussion to actually put a value in
the deadline I had left open.
> 3. Localization
> * Existing translations: Pootle is now tracking the 4.2.0 release, so
> translators do not have an immediate way to fix translations for 4.1.2.
> There is a possibility to check whether we can reuse the 4.2.0 strings
> for 4.1.2, but due to the version clash I would prefer to fix strings
> upon request, in the SDF files directly and only in the case of major,
> well-defined bugs (example: the Italian version has a typo in a main
> menu item; it is fixed in Pootle for 4.2.0 AND we can edit the SDF file
> manually to fix it for the 4.1.x line).
This is now explained better in
http://markmail.org/message/ibg5nllq7ftf6qpv ; the deadline I suggest is
July 31st.
Note that I consider this to be low-priority since this is a x.y.2
release, strings are unchanged and translations were all at 100%; so it
makes sense to only include "blocker" translation bugs in 4.1.2. But I
would definitely be happy if someone has time and knowledge for reusing
the 4.2.0 translations in 4.1.2 in a safe way; just it seems overkill
and technically not optimal.
> * New translations: same problem with Pootle; we don't have any new
> translations (additional with respect to 4.1.1) ready at the moment; if
> a translation reaches 100%, I'm available to investigate better what we
> can do with the Pootle 4.2.0 strings for 4.1.2, since that would be the
> most logical solution.
Same: this is now explained better in
http://markmail.org/message/ibg5nllq7ftf6qpv ; the deadline I suggest is
July 31st.
> * Existing dictionaries: no problem, we will integrate them as usual. A
> deadline will be agreed upon and sent to the l10n list.
> * New dictionaries: no problem, we will integrate them as usual. A
> deadline will be agreed upon and sent to the l10n list.
We keep dictionaries pending, waiting for the Extensions site to be
fully available again; but this is a straightforward fix that does not
require translation volunteers and that can come also late in the
process: we want to minimize the "Dictionary Updates Available" warnings
for new installations.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE] Contents of OpenOffice 4.1.2
Posted by jan i <ja...@apache.org>.
On 13 July 2015 at 10:19, Gavin McDonald <ga...@16degrees.com.au> wrote:
> With regards to digital signing, we have ‘test’ credits that can be used to
> practice on.
>
I understood earlier on David, that the credits infra bought last year
would expire this august and he was in doubt
how much he would buy going forward.
Do you have more recent information ?
rgds
jan i.
>
> Gav…
>
> > On 13 Jul 2015, at 9:04 am, jan i <ja...@apache.org> wrote:
> >
> > Hi
> >
> > I agree to use this as the overall plan, which of course needs to
> detailed.
> >
> > I do have a comment about digital signing. It is correct than I do not
> have
> > spare
> > cycles before mid october.
> >
> > Digital signing means in reality white listing the content, which are
> both
> > our
> > exe as well as many third part DLLs (some of the libraries are statically
> > linked
> > and not exposed outside the exe).
> >
> > Most of our third party libraries are pretty old (but works well for our
> > purpose),
> > and some of them have known security isses (not in the parts AOO uses).
> We
> > need to upgrade the libraries that uses a DLL, otherwise we might
> whitelist
> > a
> > DLL with known security issues. This process is something we should do
> > ahead of every release, and is not as such part of the digital signing,
> but
> > digital
> > signing makes it much more important.
> >
> > rgds
> > jan I.
> >
> >
> > On Sunday, July 12, 2015, Marcus <ma...@wtnet.de> wrote:
> >
> >> Am 07/12/2015 03:57 PM, schrieb Andrea Pescetti:
> >>
> >>> It's time to decide what goes into 4.1.2 and what doesn't. Not in terms
> >>> of specific bugfixes (we have the standard process of nominating
> release
> >>> blockers for this and I don't plan to change it), but in terms of
> >>> categories. The following is a realistic list of what we can have in
> >>> 4.1.2. Shall we take it as the overall plan for 4.1.2?
> >>>
> >>
> >> In general I see it the same way. Some comments inline.
> >
> >
> >>
> >>
> >> 2. Features
> >>>
> >>> * Windows 10: Millions of our users will run Windows 10 within a few
> >>> weeks. OpenOffice is reported to work smoothly on Windows 10
> >>> pre-releases. Should any major Windows 10 incompatibilities appear,
> they
> >>> should be fixed in 4.1.2.
> >>>
> >>
> >> When we want to react on specific bug reports (we should do this in any
> >> case as Windows is still the most favorite platform) then we create
> >> automatically a release schedule of a few weeks after that date - which
> is
> >> for me late summer. Just to be sure we understand the same.
> >>
> >> BTW:
> >> Release date of Win10 is July, 29th.
> >>
> >> 3. Localization
> >>>
> >>> * Existing translations: Pootle is now tracking the 4.2.0 release, so
> >>> translators do not have an immediate way to fix translations for 4.1.2.
> >>> There is a possibility to check whether we can reuse the 4.2.0 strings
> >>> for 4.1.2, but due to the version clash I would prefer to fix strings
> >>> upon request, in the SDF files directly and only in the case of major,
> >>> well-defined bugs (example: the Italian version has a typo in a main
> >>> menu item; it is fixed in Pootle for 4.2.0 AND we can edit the SDF file
> >>> manually to fix it for the 4.1.x line).
> >>>
> >>
> >> This has also the advantage (when we don't get too many change requests)
> >> that we know in detail what is changing.
> >>
> >> Marcus
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >> For additional commands, e-mail: dev-help@openoffice.apache.org
> >>
> >>
> >
> > --
> > Sent from My iPad, sorry for any misspellings.
>
> Gav...
>
> ( ( (
> ( )\ ) )\ ) )\ ) ( )
> )
> )\ (()/((()/( (()/( )\ ) ( ) ( /( ( (
> ( /( ( ( (
> ((((_)( /(_))/(_)) /(_)) ( (()/( )( ( /( ( )\()))( ))\ (
> )\()) ))\ )( ))\
> )\ _ )\ (_)) (_))_| (_)) )\ ) /(_))(()\ )(_)) )\ (_))/(()\ /((_) )\
> (_))/ /((_)(()\ /((_)
> (_)_\(_)/ __|| |_ |_ _| _(_/((_) _| ((_)((_)_ ((_)| |_ ((_)(_))(
> ((_)| |_ (_))( ((_)(_))
> / _ \ \__ \| __| | | | ' \))| _|| '_|/ _` |(_-<| _|| '_|| || |/ _|
> | _|| || || '_|/ -_)
> /_/ \_\ |___/|_| |___||_||_| |_| |_| \__,_|/__/ \__||_| \_,_|\__|
> \__| \_,_||_| \___|
>
>
>
>
>
>
Re: [RELEASE] Contents of OpenOffice 4.1.2
Posted by Gavin McDonald <ga...@16degrees.com.au>.
With regards to digital signing, we have ‘test’ credits that can be used to
practice on.
Gav…
> On 13 Jul 2015, at 9:04 am, jan i <ja...@apache.org> wrote:
>
> Hi
>
> I agree to use this as the overall plan, which of course needs to detailed.
>
> I do have a comment about digital signing. It is correct than I do not have
> spare
> cycles before mid october.
>
> Digital signing means in reality white listing the content, which are both
> our
> exe as well as many third part DLLs (some of the libraries are statically
> linked
> and not exposed outside the exe).
>
> Most of our third party libraries are pretty old (but works well for our
> purpose),
> and some of them have known security isses (not in the parts AOO uses). We
> need to upgrade the libraries that uses a DLL, otherwise we might whitelist
> a
> DLL with known security issues. This process is something we should do
> ahead of every release, and is not as such part of the digital signing, but
> digital
> signing makes it much more important.
>
> rgds
> jan I.
>
>
> On Sunday, July 12, 2015, Marcus <ma...@wtnet.de> wrote:
>
>> Am 07/12/2015 03:57 PM, schrieb Andrea Pescetti:
>>
>>> It's time to decide what goes into 4.1.2 and what doesn't. Not in terms
>>> of specific bugfixes (we have the standard process of nominating release
>>> blockers for this and I don't plan to change it), but in terms of
>>> categories. The following is a realistic list of what we can have in
>>> 4.1.2. Shall we take it as the overall plan for 4.1.2?
>>>
>>
>> In general I see it the same way. Some comments inline.
>
>
>>
>>
>> 2. Features
>>>
>>> * Windows 10: Millions of our users will run Windows 10 within a few
>>> weeks. OpenOffice is reported to work smoothly on Windows 10
>>> pre-releases. Should any major Windows 10 incompatibilities appear, they
>>> should be fixed in 4.1.2.
>>>
>>
>> When we want to react on specific bug reports (we should do this in any
>> case as Windows is still the most favorite platform) then we create
>> automatically a release schedule of a few weeks after that date - which is
>> for me late summer. Just to be sure we understand the same.
>>
>> BTW:
>> Release date of Win10 is July, 29th.
>>
>> 3. Localization
>>>
>>> * Existing translations: Pootle is now tracking the 4.2.0 release, so
>>> translators do not have an immediate way to fix translations for 4.1.2.
>>> There is a possibility to check whether we can reuse the 4.2.0 strings
>>> for 4.1.2, but due to the version clash I would prefer to fix strings
>>> upon request, in the SDF files directly and only in the case of major,
>>> well-defined bugs (example: the Italian version has a typo in a main
>>> menu item; it is fixed in Pootle for 4.2.0 AND we can edit the SDF file
>>> manually to fix it for the 4.1.x line).
>>>
>>
>> This has also the advantage (when we don't get too many change requests)
>> that we know in detail what is changing.
>>
>> Marcus
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>>
>
> --
> Sent from My iPad, sorry for any misspellings.
Gav...
( ( (
( )\ ) )\ ) )\ ) ( ) )
)\ (()/((()/( (()/( )\ ) ( ) ( /( ( ( ( /( ( ( (
((((_)( /(_))/(_)) /(_)) ( (()/( )( ( /( ( )\()))( ))\ ( )\()) ))\ )( ))\
)\ _ )\ (_)) (_))_| (_)) )\ ) /(_))(()\ )(_)) )\ (_))/(()\ /((_) )\ (_))/ /((_)(()\ /((_)
(_)_\(_)/ __|| |_ |_ _| _(_/((_) _| ((_)((_)_ ((_)| |_ ((_)(_))( ((_)| |_ (_))( ((_)(_))
/ _ \ \__ \| __| | | | ' \))| _|| '_|/ _` |(_-<| _|| '_|| || |/ _| | _|| || || '_|/ -_)
/_/ \_\ |___/|_| |___||_||_| |_| |_| \__,_|/__/ \__||_| \_,_|\__| \__| \_,_||_| \___|
Re: [RELEASE] Contents of OpenOffice 4.1.2
Posted by jan i <ja...@apache.org>.
Hi
I agree to use this as the overall plan, which of course needs to detailed.
I do have a comment about digital signing. It is correct than I do not have
spare
cycles before mid october.
Digital signing means in reality white listing the content, which are both
our
exe as well as many third part DLLs (some of the libraries are statically
linked
and not exposed outside the exe).
Most of our third party libraries are pretty old (but works well for our
purpose),
and some of them have known security isses (not in the parts AOO uses). We
need to upgrade the libraries that uses a DLL, otherwise we might whitelist
a
DLL with known security issues. This process is something we should do
ahead of every release, and is not as such part of the digital signing, but
digital
signing makes it much more important.
rgds
jan I.
On Sunday, July 12, 2015, Marcus <ma...@wtnet.de> wrote:
> Am 07/12/2015 03:57 PM, schrieb Andrea Pescetti:
>
>> It's time to decide what goes into 4.1.2 and what doesn't. Not in terms
>> of specific bugfixes (we have the standard process of nominating release
>> blockers for this and I don't plan to change it), but in terms of
>> categories. The following is a realistic list of what we can have in
>> 4.1.2. Shall we take it as the overall plan for 4.1.2?
>>
>
> In general I see it the same way. Some comments inline.
>
>
> 2. Features
>>
>> * Windows 10: Millions of our users will run Windows 10 within a few
>> weeks. OpenOffice is reported to work smoothly on Windows 10
>> pre-releases. Should any major Windows 10 incompatibilities appear, they
>> should be fixed in 4.1.2.
>>
>
> When we want to react on specific bug reports (we should do this in any
> case as Windows is still the most favorite platform) then we create
> automatically a release schedule of a few weeks after that date - which is
> for me late summer. Just to be sure we understand the same.
>
> BTW:
> Release date of Win10 is July, 29th.
>
> 3. Localization
>>
>> * Existing translations: Pootle is now tracking the 4.2.0 release, so
>> translators do not have an immediate way to fix translations for 4.1.2.
>> There is a possibility to check whether we can reuse the 4.2.0 strings
>> for 4.1.2, but due to the version clash I would prefer to fix strings
>> upon request, in the SDF files directly and only in the case of major,
>> well-defined bugs (example: the Italian version has a typo in a main
>> menu item; it is fixed in Pootle for 4.2.0 AND we can edit the SDF file
>> manually to fix it for the 4.1.x line).
>>
>
> This has also the advantage (when we don't get too many change requests)
> that we know in detail what is changing.
>
> Marcus
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
--
Sent from My iPad, sorry for any misspellings.
Re: [RELEASE] Contents of OpenOffice 4.1.2
Posted by Marcus <ma...@wtnet.de>.
Am 07/12/2015 03:57 PM, schrieb Andrea Pescetti:
> It's time to decide what goes into 4.1.2 and what doesn't. Not in terms
> of specific bugfixes (we have the standard process of nominating release
> blockers for this and I don't plan to change it), but in terms of
> categories. The following is a realistic list of what we can have in
> 4.1.2. Shall we take it as the overall plan for 4.1.2?
In general I see it the same way. Some comments inline.
> 2. Features
>
> * Windows 10: Millions of our users will run Windows 10 within a few
> weeks. OpenOffice is reported to work smoothly on Windows 10
> pre-releases. Should any major Windows 10 incompatibilities appear, they
> should be fixed in 4.1.2.
When we want to react on specific bug reports (we should do this in any
case as Windows is still the most favorite platform) then we create
automatically a release schedule of a few weeks after that date - which
is for me late summer. Just to be sure we understand the same.
BTW:
Release date of Win10 is July, 29th.
> 3. Localization
>
> * Existing translations: Pootle is now tracking the 4.2.0 release, so
> translators do not have an immediate way to fix translations for 4.1.2.
> There is a possibility to check whether we can reuse the 4.2.0 strings
> for 4.1.2, but due to the version clash I would prefer to fix strings
> upon request, in the SDF files directly and only in the case of major,
> well-defined bugs (example: the Italian version has a typo in a main
> menu item; it is fixed in Pootle for 4.2.0 AND we can edit the SDF file
> manually to fix it for the 4.1.x line).
This has also the advantage (when we don't get too many change requests)
that we know in detail what is changing.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org