On 07/15/2015 01:07 PM, Marcus wrote:
> Am 07/15/2015 07:29 PM, schrieb jan i:
>> On 15 July 2015 at 02:35, Andrea Pescetti wrote:
>>
>>> I can't expect people to read all lists, so a short update to say
>>> that the
>>> first small batch of release blockers for 4.1.2 was integrated.
>>>
>>
>> T
> On 16 Jul 2015, at 9:10 pm, Andrea Pescetti wrote:
>
> Marcus wrote:
>> Am 07/16/2015 12:05 AM, schrieb jan i:
>>> I am not sure how the procedure works, but we need to secure that the
>>> rat-scan patches (gavin) are in 4.1.2
>> Kay and Regina have committed the remaining stuff to Trunk. So,
On 15/07/2015 bugzilla wrote:
bmarcelly has asked for 4.1.2_release_blocker:
Issue 126111: Undocumented changes for annotations
https://bz.apache.org/ooo/show_bug.cgi?id=126111
(Copying comment from issue)
Do I understand correctly that you would simply like to perform a
documentation update
Marcus wrote:
Am 07/16/2015 12:05 AM, schrieb jan i:
I am not sure how the procedure works, but we need to secure that the
rat-scan patches (gavin) are in 4.1.2
Kay and Regina have committed the remaining stuff to Trunk. So, a merge
to the 4.1.2 branch/tag should be all that needs to be done.
We're on top of the problem, hope to be able to provide an update soon.
Roberto
2015-07-16 20:53 GMT+02:00 Rory O'Farrell :
> On Thu, 16 Jul 2015 20:44:10 +0200
> David Billing wrote:
>
> > No links to extensions seems to work.
> > I'm trying to get dictionaries in english.
> >
> > http://exten
On Thu, 16 Jul 2015 20:44:10 +0200
David Billing wrote:
> No links to extensions seems to work.
> I'm trying to get dictionaries in english.
>
> http://extensions.openoffice.org/
>
> Kind regards
> David Billing
The SourceForge servers, where he files are stored, seem to be down at present.
-
No links to extensions seems to work.
I'm trying to get dictionaries in english.
http://extensions.openoffice.org/
Kind regards
David Billing
On 07/15/2015 05:28 AM, Aptitude Testing Team wrote:
> On 19 May 2015 Aptitude Testing Team wrote
>> Back in May 2014, I submitted a patch fixing this issue. I understand
>> that we have to be careful implementing it, due to the location of the
>> bug.
>>
>> We have had no responses from the 13 us