Hi Peter,
Am 13.11.18 um 08:04 schrieb Peter Kovacs:
> Release is now in the svn branch.
>
> I remove tonight the 4.1.5 release, any objections?
If you speak of
https://www.apache.org/dist/openoffice/4.1.5/
our project page [1] still points to it, so please wait until the page
is updated after
Release is now in the svn branch.
I remove tonight the 4.1.5 release, any objections?
So how much time do we need? is release date 16th November feasable?
On 13.11.18 01:30, Peter Kovacs wrote:
> Andrea,
>
> I am just saying a 4.1.7 release has nothing to do with the efforts we
> have to organiz
Hi RonS
What is a disk image? OpenOffice is packed as one executable dmg file.
These questions are better asked on us...@openoffice.apache.org.
All the best
Peter
On 13.11.18 01:22, Ron Slayton wrote:
> I see in finder on my MacBook Pro that I have 2 disk images on my MacBook. Is
> that norma
I see in finder on my MacBook Pro that I have 2 disk images on my MacBook. Is
that normal. years ago when I started using AOO I may have mistakingly loaded 2
versions, although I'm not sure. If I delete one version for disk space reasons
is that likely anything negative could happen?
RonS
Andrea,
I am just saying a 4.1.7 release has nothing to do with the efforts we
have to organize for 4.2.0.
I hope I upload now into the right place, but I have initiated the task.
All the best
Peter
On 13.11.18 00:48, Andrea Pescetti wrote:
> Peter Kovacs wrote:
>> I do not see your issue. Our
On 11/12/2018 4:34 PM, Matthias Seidel wrote:
> Hi Marcus,
>
> Am 12.11.18 um 21:05 schrieb Marcus:
>> Am 12.11.18 um 14:59 schrieb Matthias Seidel:
>>> Am 11.11.18 um 17:36 schrieb Peter Kovacs:
I am not available at the moment for release manager. But it would be
good to continue,
Am 13.11.18 um 00:48 schrieb Andrea Pescetti:
> Peter Kovacs wrote:
>> I do not see your issue. Our release team works much faster then the dev
>> team progresses on 4.2.0.
>
> There is a major difference between a 4.1.x and a new release like
> 4.2.0: for 4.2.0 we need the entire community, not on
Peter Kovacs wrote:
I do not see your issue. Our release team works much faster then the dev
team progresses on 4.2.0.
There is a major difference between a 4.1.x and a new release like
4.2.0: for 4.2.0 we need the entire community, not only what you call
the "release team" and developers (re
On 12/11/2018 Matthias Seidel wrote:
Just to be clear, I wasn't thinking about taking the dictionary directly
from Opentaal.org but rather how we get the updated dictionary uploaded
to SourceForge.
Yes, this was clear. We simply mirror it on the Extensions site (not
SourceForge per se, as we m
I do not see your issue. Our release team works much faster then the dev
team progresses on 4.2.0.
And to train releases is vital for us. 4.1.6 did not really bind any
developer, beyond security issues.
A 4.1.7 will keep the routine and knowledge active while we develop 4.2.0.
All the best
Pet
On 12/11/2018 Patricia Shanahan wrote:
The way I see it, we should be keeping 4.1.x for security fixes that
cannot wait until 4.2.0. As such, we may need to decide to release 4.1.7
at any time.
Sure, this is obvious. Thanks for pointing it out and of course I agree
with it. I was commenting o
On 11/12/2018 2:49 PM, Andrea Pescetti wrote:
On 11/11/2018 Peter Kovacs wrote:
I suggest that we start right away with an Parallel development of 4.1.7
Release branch.
First, we'll have to officially release and announce 4.1.6.
Then energy should really go to 4.2.0. Only if there are any
On 11/11/2018 Peter Kovacs wrote:
I suggest that we start right away with an Parallel development of 4.1.7
Release branch.
First, we'll have to officially release and announce 4.1.6.
Then energy should really go to 4.2.0. Only if there are any outstanding
bugs or regressions we should release
Hi Andrea,
Am 12.11.18 um 23:28 schrieb Andrea Pescetti:
> Matthias Seidel wrote:
>> https://extensions.openoffice.org/en/project/dutch-spelling-and-hyphenation-dictionary
>>
>> version 200g was also taken from Opentaal.org and uploaded to
>> SourceForge.
>> Since users complain about problems wit
Matthias Seidel wrote:
https://extensions.openoffice.org/en/project/dutch-spelling-and-hyphenation-dictionary
version 200g was also taken from Opentaal.org and uploaded to SourceForge.
Since users complain about problems with this version I would really
like to bundle the updated dictionary in 4.
Mechtilde wrote:
My first problem is to extract an actual SDF Template ...
I followed the intructions in the wiki and the slides from FOSDEM 2018.
Please find more comprehensive information here:
https://s.apache.org/Dukc
This is a set of messages I sent to the dev list with everything I
man
Peter Kovacs wrote:
openoffice.org3.4-freedesktop-menus-3.4-9593.noarch.rpm
openoffice.org3.4-redhat-menus-3.4-9593.noarch.rpm
openoffice.org3.4-mandriva-menus-3.4-9593.noarch.rpm
openoffice.org3.4-suse-menus-3.4-9593.noarch.rpm
These are highly experimental test versions. Even when we agreed th
Hi Marcus,
Am 12.11.18 um 21:05 schrieb Marcus:
> Am 12.11.18 um 14:59 schrieb Matthias Seidel:
>> Am 11.11.18 um 17:36 schrieb Peter Kovacs:
>>>
>>> I am not available at the moment for release manager. But it would be
>>> good to continue, to be able to have release versions prepared.
>>
>> Back
On 11/12/2018 11:19 AM, Matthias Seidel wrote:
Hi Kay,
Am 12.11.18 um 20:10 schrieb Kay Schenk:
Hello all --
I have not gone through this course myself but it may be useful.
https://www.linux.com/blog/get-introduction-open-source-git-and-linux-new-training-cour
Page not found... It is:
h
Hi Marcus,
Am 12.11.18 um 21:03 schrieb Marcus:
> Am 12.11.18 um 20:49 schrieb Matthias Seidel:
>> Am 12.11.18 um 20:41 schrieb Marcus:
>>> I don't know were to check this in the code, therefore I'm asking here.
>>>
>>> Is it true that we bundle an outdated Dutch dictionary with any new
>>> AOO re
Hello
Am 11.11.18 um 09:37 schrieb Mechtilde:
> Hello,
>
> after doing a successful building of Apache OpenOffice I want to help
> working on a better translation (process)
>
> My first problem is to extract an actual SDF Template
>
> I followed the intructions in the wiki and the slides from F
Am 12.11.18 um 20:49 schrieb Matthias Seidel:
Am 12.11.18 um 20:41 schrieb Marcus:
I don't know were to check this in the code, therefore I'm asking here.
Is it true that we bundle an outdated Dutch dictionary with any new
AOO release?
Yes, we take the latest Dutch dictionary available on Sou
Am 12.11.18 um 14:59 schrieb Matthias Seidel:
Am 11.11.18 um 17:36 schrieb Peter Kovacs:
I am not available at the moment for release manager. But it would be
good to continue, to be able to have release versions prepared.
Back to 4.1.6: Is anyone already working on the Release Notes?
compa
Hi Marcus,
Am 12.11.18 um 20:41 schrieb Marcus:
> I don't know were to check this in the code, therefore I'm asking here.
>
> Is it true that we bundle an outdated Dutch dictionary with any new
> AOO release?
Yes, we take the latest Dutch dictionary available on SourceForge (v2.00g).
https://svn
I don't know were to check this in the code, therefore I'm asking here.
Is it true that we bundle an outdated Dutch dictionary with any new AOO
release?
Thanks
Marcus
Am 10.11.18 um 20:34 schrieb bugzi...@apache.org:
https://bz.apache.org/ooo/show_bug.cgi?id=127932
Issue ID: 1
Am 12.11.18 um 14:39 schrieb Jim Jagielski:
On Nov 11, 2018, at 11:36 AM, Peter Kovacs wrote:
And I suggest also to branch 4.2.0 from trunk. Jim you still available
to be the release manager on this branch? - Maybe we should branch from
the latest dev build version if we can find out and then
Hi Kay,
Am 12.11.18 um 20:10 schrieb Kay Schenk:
> Hello all --
>
> I have not gone through this course myself but it may be useful.
>
> https://www.linux.com/blog/get-introduction-open-source-git-and-linux-new-training-cour
>
Page not found... It is:
https://www.linux.com/blog/get-introduction-
On 11/12/2018 05:39 AM, Jim Jagielski wrote:
On Nov 11, 2018, at 11:36 AM, Peter Kovacs wrote:
And I suggest also to branch 4.2.0 from trunk. Jim you still available
to be the release manager on this branch? - Maybe we should branch from
the latest dev build version if we can find out and t
Hello all --
I have not gone through this course myself but it may be useful.
https://www.linux.com/blog/get-introduction-open-source-git-and-linux-new-training-cour
--
MzK
"Less is MORE."
Hi Peter,
Am 11.11.18 um 17:36 schrieb Peter Kovacs:
> Hello all,
>
> I suggest that we start right away with an Parallel development of 4.1.7
> Release branch. I nominate Matthias to be release manager. Are you
> willing to go on this?
Yes, after we have 4.1.6 out I will take a deep breath and b
Hello,
Am 12.11.18 um 14:39 schrieb Jim Jagielski:
>
>
>> On Nov 11, 2018, at 11:36 AM, Peter Kovacs wrote:
>>
>> And I suggest also to branch 4.2.0 from trunk. Jim you still available
>> to be the release manager on this branch? - Maybe we should branch from
>> the latest dev build version if
> On Nov 11, 2018, at 11:36 AM, Peter Kovacs wrote:
>
> And I suggest also to branch 4.2.0 from trunk. Jim you still available
> to be the release manager on this branch? - Maybe we should branch from
> the latest dev build version if we can find out and then check on the
> commits.
That work
32 matches
Mail list logo
