Re: A 4.1.6 Release

2018-09-18 Thread Jim Jagielski
Thats right :) > On Sep 15, 2018, at 4:07 AM, Matthias Seidel > wrote: > > Am 15.09.2018 um 07:47 schrieb Peter Kovacs: >> Okay for granting I switch from '?' to none? > > No, you change to "+" if you think this should be in 4.1.6. > And you change to "-" if you think it shouldn't. > > At lea

Re: A 4.1.6 Release

2018-09-16 Thread Peter Kovacs
+1 On 9/16/18 10:21 PM, Matthias Seidel wrote: Am 16.09.2018 um 22:08 schrieb Peter Kovacs: Odd they are not on my filter list. yea they are fine. should we change milestone now too? I did for one issue (already committed) But the other one hasn't 4.1.6 in the list. @Marcus: Maybe you can he

Re: A 4.1.6 Release

2018-09-16 Thread Matthias Seidel
Am 16.09.2018 um 22:08 schrieb Peter Kovacs: > Odd they are not on my filter list. yea they are fine. > > should we change milestone now too? I did for one issue (already committed) But the other one hasn't 4.1.6 in the list. @Marcus: Maybe you can help (again)? https://bz.apache.org/ooo/show_bu

Re: A 4.1.6 Release

2018-09-16 Thread Peter Kovacs
Odd they are not on my filter list. yea they are fine. should we change milestone now too? On 9/16/18 10:02 PM, Matthias Seidel wrote: Am 16.09.2018 um 21:59 schrieb Peter Kovacs: No Idea. I have 10 issues on the list. Maybe they do not have a release blocker? https://bz.apache.org/ooo/show_

Re: A 4.1.6 Release

2018-09-16 Thread Matthias Seidel
Am 16.09.2018 um 21:59 schrieb Peter Kovacs: > No Idea. I have 10 issues on the list. Maybe they do not have a > release blocker? https://bz.apache.org/ooo/show_bug.cgi?id=74793 https://bz.apache.org/ooo/show_bug.cgi?id=126736 According to Marcus I could grant them myself. And I could commit them

Re: A 4.1.6 Release

2018-09-16 Thread Peter Kovacs
No Idea. I have 10 issues on the list. Maybe they do not have a release blocker? On 9/16/18 9:56 PM, Matthias Seidel wrote: Hi Peter, Am 16.09.2018 um 11:29 schrieb Peter Kovacs: Awesome! thanks a lot. + I managed to switch my user account to the committer email, yay. And I managed to query

Re: A 4.1.6 Release

2018-09-16 Thread Matthias Seidel
Hi Peter, Am 16.09.2018 um 11:29 schrieb Peter Kovacs: > Awesome! thanks a lot. > > + I managed to switch my user account to the committer email, yay. > > And I managed to query for the flag, and chgecked all suggestions and > worked them through. Thanks! You left two requests (from me) open... M

Re: A 4.1.6 Release

2018-09-16 Thread Peter Kovacs
Awesome! thanks a lot. + I managed to switch my user account to the committer email, yay. And I managed to query for the flag, and chgecked all suggestions and worked them through. On 9/16/18 11:12 AM, Marcus wrote: Am 15.09.2018 um 10:34 schrieb Matthias Seidel: Am 15.09.2018 um 10:07 schr

Re: A 4.1.6 Release

2018-09-16 Thread Marcus
Am 15.09.2018 um 10:34 schrieb Matthias Seidel: Am 15.09.2018 um 10:07 schrieb Matthias Seidel: Am 15.09.2018 um 07:47 schrieb Peter Kovacs: Okay for granting I switch from '?' to none? No, you change to "+" if you think this should be in 4.1.6. And you change to "-" if you think it shouldn't.

Re: A 4.1.6 Release

2018-09-15 Thread Matthias Seidel
Am 15.09.2018 um 20:25 schrieb Peter kovacs: > I do not have those rights. Probably because my bugzilla user is an account. > I tried to switch to my apache address but I failed. > The account name is an leginee account at Google mail service. Your account must be added to the appropriate groups.

Re: A 4.1.6 Release

2018-09-15 Thread Peter kovacs
I do not have those rights. Probably because my bugzilla user is an account. I tried to switch to my apache address but I failed. The account name is an leginee account at Google mail service. Am 15. September 2018 10:34:31 MESZ schrieb Matthias Seidel : >Am 15.09.2018 um 10:07 schrieb Matthias

Re: A 4.1.6 Release

2018-09-15 Thread Matthias Seidel
Am 15.09.2018 um 10:07 schrieb Matthias Seidel: > Am 15.09.2018 um 07:47 schrieb Peter Kovacs: >> Okay for granting I switch from '?' to none? > No, you change to "+" if you think this should be in 4.1.6. > And you change to "-" if you think it shouldn't. > > At least this is my understanding... T

Re: A 4.1.6 Release

2018-09-15 Thread Matthias Seidel
Am 15.09.2018 um 07:47 schrieb Peter Kovacs: > Okay for granting I switch from '?' to none? No, you change to "+" if you think this should be in 4.1.6. And you change to "-" if you think it shouldn't. At least this is my understanding... Regards,    Matthias > > On 9/14/18 7:37 PM, Matthias Sei

Re: A 4.1.6 Release

2018-09-14 Thread Peter Kovacs
Okay for granting I switch from '?' to none? On 9/14/18 7:37 PM, Matthias Seidel wrote: Hi Peter, Am 09.09.2018 um 18:03 schrieb Peter Kovacs: Okay I had a look now. I have a bit of an issue in filtering on the blocker flag. I filtered now on the Version 4.1.6-dev and 4.1.6 and found 6 repor

Re: A 4.1.6 Release

2018-09-14 Thread Matthias Seidel
Hi Peter, Am 09.09.2018 um 18:03 schrieb Peter Kovacs: > Okay I had a look now. > > I have a bit of an issue in filtering on the blocker flag. > > I filtered now on the Version 4.1.6-dev and 4.1.6 and found 6 reports. > > Are these all of them? > > > - The Patch I had in mind i did not find again.

Re: A 4.1.6 Release

2018-09-12 Thread Matthias Seidel
Hi Andrea, Am 03.09.2018 um 22:37 schrieb Andrea Pescetti: > Matthias Seidel wrote: >> How about this one: >> https://bz.apache.org/ooo/show_bug.cgi?id=126736 >> It fixes a typo in the build process. > > This one has zero impact for users and, if 4.1.6 was just a > maintenance release and we had r

Re: A 4.1.6 Release

2018-09-10 Thread Keith N. McKenna
On 9/10/2018 2:56 PM, Kay Schenk wrote: > On Mon, Sep 10, 2018 at 10:02 AM, Keith N. McKenna < > keith.mcke...@comcast.net> wrote: > >> On 9/10/2018 12:17 PM, Kay Schenk wrote: >>> On Sun, Sep 9, 2018 at 3:47 PM, Kay Schenk wrote: >>> On Sun, Sep 9, 2018, 15:43 Keith N. McKenna >>

Re: A 4.1.6 Release

2018-09-10 Thread Kay Schenk
On Mon, Sep 10, 2018 at 10:02 AM, Keith N. McKenna < keith.mcke...@comcast.net> wrote: > On 9/10/2018 12:17 PM, Kay Schenk wrote: > > On Sun, Sep 9, 2018 at 3:47 PM, Kay Schenk wrote: > > > >> > >> > >> On Sun, Sep 9, 2018, 15:43 Keith N. McKenna > >> wrote: > >> > >>> > > I had been

Re: A 4.1.6 Release

2018-09-10 Thread Keith N. McKenna
On 9/10/2018 12:17 PM, Kay Schenk wrote: > On Sun, Sep 9, 2018 at 3:47 PM, Kay Schenk wrote: > >> >> >> On Sun, Sep 9, 2018, 15:43 Keith N. McKenna >> wrote: >> >>> I had been constructing release blocker queries for some of the other releases. I just put together a que

Re: A 4.1.6 Release

2018-09-10 Thread Kay Schenk
On Sun, Sep 9, 2018 at 3:47 PM, Kay Schenk wrote: > > > On Sun, Sep 9, 2018, 15:43 Keith N. McKenna > wrote: > >> >> > >> > I had been constructing release blocker queries for some of the other >> > releases. >> > >> > I just put together a query for the release block requests for 4.1.6 -- >> >

Re: A 4.1.6 Release

2018-09-09 Thread Andrea Pescetti
On 09/09/2018 Matthias Seidel wrote: But I know that Andrea wanted to ask for a blocker, but we hadn't enabled the flag at that time. It worked now: https://bz.apache.org/ooo/show_bug.cgi?id=127712 Regards, Andrea. - To uns

Re: A 4.1.6 Release

2018-09-09 Thread Kay Schenk
On Sun, Sep 9, 2018, 15:43 Keith N. McKenna wrote: > > > > > I had been constructing release blocker queries for some of the other > > releases. > > > > I just put together a query for the release block requests for 4.1.6 -- > > > > > https://bz.apache.org/ooo/buglist.cgi?cmdtype=dorem&list_id=2

Re: A 4.1.6 Release

2018-09-09 Thread Keith N. McKenna
> > I had been constructing release blocker queries for some of the other > releases. > > I just put together a query for the release block requests for 4.1.6 -- > > https://bz.apache.org/ooo/buglist.cgi?cmdtype=dorem&list_id=236879&namedcmd=4.1.6_blocker_requested&remaction=run > (I didn't do

Re: A 4.1.6 Release

2018-09-09 Thread Kay Schenk
Hi all -- On Sun, Sep 9, 2018 at 10:06 AM, Matthias Seidel wrote: > Hi Peter, > > Am 09.09.2018 um 18:03 schrieb Peter Kovacs: > > Okay I had a look now. > > > > I have a bit of an issue in filtering on the blocker flag. > > > > I filtered now on the Version 4.1.6-dev and 4.1.6 and found 6 repor

Re: A 4.1.6 Release

2018-09-09 Thread Matthias Seidel
Hi Peter, Am 09.09.2018 um 18:03 schrieb Peter Kovacs: > Okay I had a look now. > > I have a bit of an issue in filtering on the blocker flag. > > I filtered now on the Version 4.1.6-dev and 4.1.6 and found 6 reports. > > Are these all of them? I don't know your list, can you post the issue numbe

Re: A 4.1.6 Release

2018-09-09 Thread Peter Kovacs
Okay I had a look now. I have a bit of an issue in filtering on the blocker flag. I filtered now on the Version 4.1.6-dev and 4.1.6 and found 6 reports. Are these all of them? - The Patch I had in mind i did not find again. Next time I have to note the issue number. :( Thus I am fine with

Re: A 4.1.6 Release

2018-09-07 Thread Matthias Seidel
Am 07.09.2018 um 14:53 schrieb Jim Jagielski: > I am going to hold off until we have some stuff in AOO416, other than > external lib upgrades, which are different from AOO415 I just wanted to do test builds to see if it builds again after some patches broke the build process... No problems at the

Re: A 4.1.6 Release

2018-09-07 Thread Jim Jagielski
I am going to hold off until we have some stuff in AOO416, other than external lib upgrades, which are different from AOO415 > On Sep 6, 2018, at 2:30 PM, Matthias Seidel > wrote: > > Am 06.09.2018 um 15:25 schrieb Jim Jagielski: >> Anyone can propose something as a blocker... it's up to the R

Re: A 4.1.6 Release

2018-09-06 Thread Matthias Seidel
Am 06.09.2018 um 15:25 schrieb Jim Jagielski: > Anyone can propose something as a blocker... it's up to the RM on whether it > really is one or not ;) > > BTW: I'm ready to go w/ Linux and macOS builds! Windows builds (based on r1839814) are up: https://home.apache.org/~mseidel/AOO-builds/AOO-416

Re: A 4.1.6 Release

2018-09-06 Thread Peter Kovacs
I plan to have a look on the weekend, what we have now. I want to add one patch concerning mailmerge. And then off we go, I Think. I agree with Jim in general. I see a possibility that the 4.1.x series gets maintenance till 2020, for centOS6 while every one else is moving to 4.2.0. Am 6. Sep

Re: A 4.1.6 Release

2018-09-06 Thread Jim Jagielski
Anyone can propose something as a blocker... it's up to the RM on whether it really is one or not ;) BTW: I'm ready to go w/ Linux and macOS builds! > On Sep 6, 2018, at 8:05 AM, Matthias Seidel > wrote: > > Hi Jim, > > Am 03.09.2018 um 23:45 schrieb Jim Jagielski: >> For some users, AOO 4.1

Re: A 4.1.6 Release

2018-09-06 Thread Matthias Seidel
Hi Jim, Am 03.09.2018 um 23:45 schrieb Jim Jagielski: > For some users, AOO 4.1.6 will be the "last" version of OO that they can use, > since AOO 4.2.x will not provide some community build for older platforms > (eg: CentOS5,...). As such, I think we need to make 4.1.6 as good and as > stable

Re: A 4.1.6 Release

2018-09-03 Thread Jim Jagielski
For some users, AOO 4.1.6 will be the "last" version of OO that they can use, since AOO 4.2.x will not provide some community build for older platforms (eg: CentOS5,...). As such, I think we need to make 4.1.6 as good and as stable and as useful, with as many patches and fixes, as feasible for

Re: A 4.1.6 Release

2018-09-03 Thread Matthias Seidel
Hi Andrea, Am 03.09.2018 um 22:37 schrieb Andrea Pescetti: > Matthias Seidel wrote: >> How about this one: >> https://bz.apache.org/ooo/show_bug.cgi?id=126736 >> It fixes a typo in the build process. > > This one has zero impact for users and, if 4.1.6 was just a > maintenance release and we had r

Re: A 4.1.6 Release

2018-09-03 Thread Andrea Pescetti
Matthias Seidel wrote: How about this one: https://bz.apache.org/ooo/show_bug.cgi?id=126736 It fixes a typo in the build process. This one has zero impact for users and, if 4.1.6 was just a maintenance release and we had regular 4.x major releases, it wouldn't make sense to include fixes like

Re: A 4.1.6 Release

2018-09-01 Thread Matthias Seidel
Hi Peter, Am 01.09.2018 um 12:03 schrieb Peter Kovacs: > Sorry. I thought I send the answer. Yes Please. Done! How about this one: https://bz.apache.org/ooo/show_bug.cgi?id=126736 It fixes a typo in the build process. Regards,    Matthias > > Am 1. September 2018 10:07:38 MESZ schrieb Matthia

Re: A 4.1.6 Release

2018-09-01 Thread Peter Kovacs
Sorry. I thought I send the answer. Yes Please. Am 1. September 2018 10:07:38 MESZ schrieb Matthias Seidel : >Hi Peter, > >any opinion on this one? >Or should I set the "release blocker" flag in bugzilla for that >purpose? > >Regards, > >   Matthias > > >Am 29.08.2018 um 18:54 schrieb Matthias Se

Re: A 4.1.6 Release

2018-09-01 Thread Matthias Seidel
Hi Peter, any opinion on this one? Or should I set the "release blocker" flag in bugzilla for that purpose? Regards,    Matthias Am 29.08.2018 um 18:54 schrieb Matthias Seidel: > Hi Peter, > > Am 29.08.2018 um 09:07 schrieb Peter Kovacs: >> This is a configuration thing. In general I do not ha

Re: A 4.1.6 Release

2018-08-29 Thread Matthias Seidel
Hi Peter, Am 29.08.2018 um 09:07 schrieb Peter Kovacs: > This is a configuration thing. In general I do not have an issue in adding > configuration changes to bugfix releases. > However this one is 16 years old and has been requested in another time and > context. > > I think we should ask the c

Re: A 4.1.6 Release

2018-08-29 Thread Matthias Seidel
Hi Jim, Am 29.08.2018 um 13:29 schrieb Jim Jagielski: > Agreed. Maybe it's a topic of discussion for 4.2.0 but not really suited for > a patch release (ie: 4.1.6) > >> On Aug 28, 2018, at 5:12 PM, Andrea Pescetti wrote: >> >> On 28/08/2018 FR web forum wrote: >>> https://bz.apache.org/ooo/show_b

Re: A 4.1.6 Release

2018-08-29 Thread Jim Jagielski
Agreed. Maybe it's a topic of discussion for 4.2.0 but not really suited for a patch release (ie: 4.1.6) > On Aug 28, 2018, at 5:12 PM, Andrea Pescetti wrote: > > On 28/08/2018 FR web forum wrote: >> https://bz.apache.org/ooo/show_bug.cgi?id=9392 >> This patch could be embedded in this release?

Re: A 4.1.6 Release

2018-08-29 Thread Peter Kovacs
This is a configuration thing. In general I do not have an issue in adding configuration changes to bugfix releases. However this one is 16 years old and has been requested in another time and context. I think we should ask the community if they like it or not. And since we want to have some in

Re: A 4.1.6 Release

2018-08-28 Thread Andrea Pescetti
On 28/08/2018 FR web forum wrote: https://bz.apache.org/ooo/show_bug.cgi?id=9392 This patch could be embedded in this release? I'm not the release manager, so this is just a personal opinion. The patch swaps the behaviour of two keys (Backspace and Del) and thus shouldn't be applied to a 4.1.

Re: A 4.1.6 Release

2018-08-28 Thread FR web forum
https://bz.apache.org/ooo/show_bug.cgi?id=9392 This patch could be embedded in this release? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: A 4.1.6 Release

2018-08-28 Thread Matthias Seidel
Hi Andrea, Am 28.08.2018 um 00:05 schrieb Andrea Pescetti: > Matthias Seidel wrote: >> Dictionary updates are no problem and done routinely in every release. > > Sure, no problem. > >> But I have yet to find the script that updates the version number. ;-) > > Here it is: > https://bz.apache.org/oo

Re: A 4.1.6 Release

2018-08-27 Thread Andrea Pescetti
Matthias Seidel wrote: Dictionary updates are no problem and done routinely in every release. Sure, no problem. But I have yet to find the script that updates the version number. ;-) Here it is: https://bz.apache.org/ooo/show_bug.cgi?id=127639 And its destination if of course somewhere und

Re: A 4.1.6 Release

2018-08-27 Thread Matthias Seidel
Hi Peter, Am 27.08.2018 um 22:07 schrieb Peter Kovacs: > Yes please bumb version number. > If there is not much complication we could also update the English dictionary. Dictionary updates are no problem and done routinely in every release. But I have yet to find the script that updates the vers

Re: A 4.1.6 Release

2018-08-27 Thread Peter Kovacs
Yes please bumb version number. If there is not much complication we could also update the English dictionary. Am 27. August 2018 19:18:26 MESZ schrieb Matthias Seidel : >Hi Peter, > >Am 27.08.2018 um 08:35 schrieb Peter kovacs: >> Thanks Matthias! > >You're welcome! > >> >> Am 26. August 2018

Re: A 4.1.6 Release

2018-08-27 Thread Matthias Seidel
Hi Peter, Am 27.08.2018 um 08:35 schrieb Peter kovacs: > Thanks Matthias! You're welcome! > > Am 26. August 2018 23:34:25 MESZ schrieb Matthias Seidel > : >> Done! >> >> Not sure about the script... Is it in devtools? We should now bump up the version number. I would like to update the Englis

Re: A 4.1.6 Release

2018-08-26 Thread Peter kovacs
Thanks Matthias! Am 26. August 2018 23:34:25 MESZ schrieb Matthias Seidel : >Done! > >Not sure about the script... Is it in devtools? > >Regards, > >   Matthias > > >Am 26.08.2018 um 23:21 schrieb Andrea Pescetti: >> Matthias Seidel wrote: >>> I could try to create the branch. Just to make sure:

Re: A 4.1.6 Release

2018-08-26 Thread Matthias Seidel
Done! Not sure about the script... Is it in devtools? Regards,    Matthias Am 26.08.2018 um 23:21 schrieb Andrea Pescetti: > Matthias Seidel wrote: >> I could try to create the branch. Just to make sure: >> >> svn copy https://svn.apache.org/repos/asf/openoffice/branches/AOO415/ >> https://svn

Re: A 4.1.6 Release

2018-08-26 Thread Andrea Pescetti
Matthias Seidel wrote: I could try to create the branch. Just to make sure: svn copy https://svn.apache.org/repos/asf/openoffice/branches/AOO415/ https://svn.apache.org/repos/asf/openoffice/branches/AOO416/ -m "Branch off 4.1.6 from HEAD of 4.1.5" is enough? Or is -r HEAD needed? Yes, that sh

Re: A 4.1.6 Release

2018-08-26 Thread Matthias Seidel
Hi Andrea, Am 26.08.2018 um 22:04 schrieb Andrea Pescetti: > Matthias Seidel wrote: >> Am 19.08.2018 um 15:13 schrieb Andrea Pescetti: >>> It does not create branches. So one would, for example, create the >>> AOO416 branch with an svn copy operation form AOO415, then run the >>> script locally to

Re: A 4.1.6 Release

2018-08-26 Thread Andrea Pescetti
Matthias Seidel wrote: Am 19.08.2018 um 15:13 schrieb Andrea Pescetti: It does not create branches. So one would, for example, create the AOO416 branch with an svn copy operation form AOO415, then run the script locally to update constants and other settings. Is there a planned date to create t

Re: A 4.1.6 Release

2018-08-26 Thread Peter kovacs
I would have done already. But the last time I had tried i could not check-in anything. So the Idea is asap. I wrote that I have dissifultiea to progress. :( Am 25. August 2018 17:33:09 MESZ schrieb Matthias Seidel : >Am 19.08.2018 um 15:13 schrieb Andrea Pescetti: >> Matthias Seidel wrote: >>

Re: A 4.1.6 Release

2018-08-25 Thread Matthias Seidel
Am 19.08.2018 um 15:13 schrieb Andrea Pescetti: > Matthias Seidel wrote: >> Just for better understanding: >> Does the script create a new branch incl. all needed changes or do we >> have to branch first and then run the script? > > It does not create branches. So one would, for example, create the

Re: A 4.1.6 Release

2018-08-21 Thread FR web forum
8:20 > Objet: Re: A 4.1.6 Release > > A good place to start is: > > https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release > > https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.5 > > > https://cwiki.apache.org/confl

Re: A 4.1.6 Release

2018-08-20 Thread Jim Jagielski
A good place to start is: https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.5 https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.6+Release+Planning

Re: A 4.1.6 Release

2018-08-20 Thread Jim Jagielski
> On Aug 17, 2018, at 1:51 AM, Peter kovacs wrote: > > I have managed to make time on the next weekend's. So I volunteer for Release > Manager. Hope it helps to get this from the table. > Great news! If you need any help, don't hesitate to ping me. I believe that as I went thru the last f

Re: A 4.1.6 Release

2018-08-20 Thread Jim Jagielski
> On Aug 18, 2018, at 11:02 AM, Andrea Pescetti wrote: > > > Yes, the Release Manager role in itself is mostly paperwork and procedures: > for OpenOffice most of the actual work goes into producing the builds. I hope > Jim can dust off his CentOS 5 and OS X VMs for "just one last time" once

Re: A 4.1.6 Release

2018-08-19 Thread Andrea Pescetti
Peter Kovacs wrote: However I am not able to access the svn. I can do that with my password right or do I need to use a passkey? Password authentication is fine. It's unlikely that your user is banned: often you will be able to reset your password at id.apache.org The KEYS file is described

Re: A 4.1.6 Release

2018-08-19 Thread Andrea Pescetti
Matthias Seidel wrote: Just for better understanding: Does the script create a new branch incl. all needed changes or do we have to branch first and then run the script? It does not create branches. So one would, for example, create the AOO416 branch with an svn copy operation form AOO415, the

Re: A 4.1.6 Release

2018-08-19 Thread Peter Kovacs
Hmpf I think I am banned. I wrote an email to infra. On 8/18/18 7:53 PM, Peter Kovacs wrote: I try my best. However I am not able to access the svn. I can do that with my password right or do I need to use a passkey? On 8/18/18 5:02 PM, Andrea Pescetti wrote: Matthias Seidel ha scritto:

Re: A 4.1.6 Release

2018-08-18 Thread Matthias Seidel
Hi Andrea, Am 18.08.2018 um 17:02 schrieb Andrea Pescetti: > Matthias Seidel ha scritto: >> Am 17.08.2018 um 07:51 schrieb Peter kovacs: >>> I have managed to make time on the next weekend's. So I volunteer >>> for Release Manager.  Hope it helps to get this from the table. >> If there would be a

Re: A 4.1.6 Release

2018-08-18 Thread Peter Kovacs
I try my best. However I am not able to access the svn. I can do that with my password right or do I need to use a passkey? On 8/18/18 5:02 PM, Andrea Pescetti wrote: Matthias Seidel ha scritto: Am 17.08.2018 um 07:51 schrieb Peter kovacs: I have managed to make time on the next weekend's.

Re: A 4.1.6 Release

2018-08-18 Thread Andrea Pescetti
Matthias Seidel ha scritto: Am 17.08.2018 um 07:51 schrieb Peter kovacs: I have managed to make time on the next weekend's. So I volunteer for Release Manager. Hope it helps to get this from the table. If there would be a role as Co-Release Manager, I would volunteer for it. That said, I beli

Re: A 4.1.6 Release

2018-08-18 Thread Matthias Seidel
al - >>>> De: "Jim Jagielski" >>>> À: "OOo Apache" >>>> Envoyé: Mercredi 25 Juillet 2018 15:48:00 >>>> Objet: Re: A 4.1.6 Release >>>> >>>> No worries. I have my VMs ready to go. >>>> >&

Re: A 4.1.6 Release

2018-08-16 Thread Peter kovacs
hance. > > >On 25.07.2018 17:18, FR web forum wrote: >> Regression: https://bz.apache.org/ooo/show_bug.cgi?id=127646 >> This release will fix it? >> >> - Mail original - >>> De: "Jim Jagielski" >>> À: "OOo Apache" >>>

Re: A 4.1.6 Release

2018-07-25 Thread Peter Kovacs
Apache" Envoyé: Mercredi 25 Juillet 2018 15:48:00 Objet: Re: A 4.1.6 Release No worries. I have my VMs ready to go. On Jul 23, 2018, at 12:47 AM, Peter kovacs wrote: Fyi: To my frustration I failed yesterday to proceed. My next timeslot is on Wednesday. I hope nothing will interfere. Am

Re: A 4.1.6 Release

2018-07-25 Thread Peter Kovacs
ake significant ripples in our eco-system and we seem to not really care about that anymore. On Jul 3, 2018, at 4:02 PM, Matthias Seidel wrote: Am 03.07.2018 um 21:45 schrieb Jim Jagielski: On Jul 1, 2018, at 11:27 AM, Peter Kovacs wrote: Hi everbody. I would like to bring a 4.1.6 Release o

Re: A 4.1.6 Release

2018-07-25 Thread FR web forum
Regression: https://bz.apache.org/ooo/show_bug.cgi?id=127646 This release will fix it? - Mail original - > De: "Jim Jagielski" > À: "OOo Apache" > Envoyé: Mercredi 25 Juillet 2018 15:48:00 > Objet: Re: A 4.1.6 Release > > No worries. I have my V

Re: A 4.1.6 Release

2018-07-25 Thread Jim Jagielski
t; Macintosh 7,8424 >>>> Unknown 4,9012 >>>> Linux 1,0621 >>>> Android 0,0762 >>>> BSD 0,0011 >>>> Solaris 0,0006 >>>> >>>> But even then, I'm sure the most downloa

Re: A 4.1.6 Release

2018-07-22 Thread Peter kovacs
ndroid 0,0762 >>> BSD 0,0011 >>> Solaris 0,0006 >>> >>> But even then, I'm sure the most downloads from resp. for Linux will >>> be for 64-bit. >>> >>> Has anybody more exact numbers - or an idea how to get them?

Re: A 4.1.6 Release

2018-07-21 Thread Marcus
e seem to not really care about that anymore. On Jul 3, 2018, at 4:02 PM, Matthias Seidel wrote: Am 03.07.2018 um 21:45 schrieb Jim Jagielski: On Jul 1, 2018, at 11:27 AM, Peter Kovacs wrote: Hi everbody. I would like to bring a 4.1.6 Release on the way in July. Even if we manage to g

Re: A 4.1.6 Release

2018-07-20 Thread Patricia Shanahan
ias Seidel wrote: Am 03.07.2018 um 21:45 schrieb Jim Jagielski: On Jul 1, 2018, at 11:27 AM, Peter Kovacs wrote: Hi everbody. I would like to bring a 4.1.6 Release on the way in July. Even if we manage to get 4.2.0 ready it will only be a beta. And we have some stuff to get out to the people.

Re: A 4.1.6 Release

2018-07-20 Thread Peter Kovacs
;>>> What impact has Ant 1.10.x exactly on older machines? >>>>>> It is no problem for me to build the Windows version with Ant >>>>>> 1.9.12. As >>>>>> long as we use Java 8. >>>>>> >>>>>> But again, I

Re: A 4.1.6 Release

2018-07-19 Thread Matthias Seidel
t;>> To be more precise: I was the only one who cared. No response from >>>>> other >>>>> members! >>>>> >>>>> >>>>> Am 03.07.2018 um 23:19 schrieb Jim Jagielski: >>>>> >>>>>> The above ma

Re: A 4.1.6 Release

2018-07-05 Thread Jim Jagielski
Considering the # of macOS related downloads, and the fact that pretty much every module that is ported to the gbuild system breaks the macOS build (currently trying to resolve the lingucomponent issues), could I suggest that we hold off on the dmake->gbuild migration for awhile? --

Re: A 4.1.6 Release

2018-07-04 Thread Kay Schenk
t;>> >>>>> Am 03.07.2018 um 23:19 schrieb Jim Jagielski: >>>>> >>>>> The above made it appear that Ant 1.9.x was no longer supported plus >>>>>> had some sort of security related issue making it unsuited for AOO.

Re: A 4.1.6 Release

2018-07-04 Thread Marcus
wrote: Am 03.07.2018 um 21:45 schrieb Jim Jagielski: On Jul 1, 2018, at 11:27 AM, Peter Kovacs wrote: Hi everbody. I would like to bring a 4.1.6 Release on the way in July. Even if we manage to get 4.2.0 ready it will only be a beta. And we have some stuff to get out to the people. Matthias ha

Re: A 4.1.6 Release

2018-07-04 Thread Kay Schenk
> >>>> How about showing some sympathy and understanding for those who may be >>>> stuck w/ older machines? After all, let's be real, our continued support >>>> for "older" systems is the only real thing we have going for us... It's >>>

Re: A 4.1.6 Release

2018-07-04 Thread Marcus
ignificant ripples in our eco-system and we seem to not really care about that anymore. On Jul 3, 2018, at 4:02 PM, Matthias Seidel wrote: Am 03.07.2018 um 21:45 schrieb Jim Jagielski: On Jul 1, 2018, at 11:27 AM, Peter Kovacs wrote: Hi everbody. I would like to bring a 4.1.6 Release on the

Re: A 4.1.6 Release

2018-07-03 Thread Peter Kovacs
stem and we seem to not really care about that anymore. On Jul 3, 2018, at 4:02 PM, Matthias Seidel wrote: Am 03.07.2018 um 21:45 schrieb Jim Jagielski: On Jul 1, 2018, at 11:27 AM, Peter Kovacs wrote: Hi everbody. I would like to bring a 4.1.6 Release on the way in July. Even if we manage to

Re: A 4.1.6 Release

2018-07-03 Thread Matthias Seidel
ples in our eco-system and we seem to > not really care about that anymore. > >> On Jul 3, 2018, at 4:02 PM, Matthias Seidel >> wrote: >> >> Am 03.07.2018 um 21:45 schrieb Jim Jagielski: >>>> On Jul 1, 2018, at 11:27 AM, Peter Kovacs wrote: >>>&g

Re: A 4.1.6 Release

2018-07-03 Thread Jim Jagielski
:02 PM, Matthias Seidel > wrote: > > Am 03.07.2018 um 21:45 schrieb Jim Jagielski: >> >>> On Jul 1, 2018, at 11:27 AM, Peter Kovacs wrote: >>> >>> Hi everbody. >>> >>> >>> I would like to bring a 4.1.6 Release on the way in Ju

Re: A 4.1.6 Release

2018-07-03 Thread Matthias Seidel
Am 03.07.2018 um 21:45 schrieb Jim Jagielski: > >> On Jul 1, 2018, at 11:27 AM, Peter Kovacs wrote: >> >> Hi everbody. >> >> >> I would like to bring a 4.1.6 Release on the way in July. Even if we manage >> to get 4.2.0 ready it will only be a beta.

Re: A 4.1.6 Release

2018-07-03 Thread Jim Jagielski
> On Jul 1, 2018, at 11:27 AM, Peter Kovacs wrote: > > Hi everbody. > > > I would like to bring a 4.1.6 Release on the way in July. Even if we manage > to get 4.2.0 ready it will only be a beta. And we have some stuff to get out > to the people. > > Matthia

Re: A 4.1.6 Release

2018-07-03 Thread Matthias Seidel
r platforms will be built) > Would 4.1.6 still be using gstreamer 0.10? Yes. > > > > On 07/01/2018 08:27 AM, Peter Kovacs wrote: >> Hi everbody. >> >> >> I would like to bring a 4.1.6 Release on the way in July. Even if we >> manage to get 4.2.0

Re: A 4.1.6 Release

2018-07-03 Thread Matthias Seidel
>>> I would like to bring a 4.1.6 Release on the way in July. Even if we manage >>> to get 4.2.0 ready it will only be a beta. And we have some stuff to get >>> out to the people. >>> Matthias has created a suggestion for a 4.1.6 release on security. >>>

Re: A 4.1.6 Release

2018-07-03 Thread Jim Jagielski
As soon as we have a repo branch setup, I'll kick off Linux and macOS builds. > On Jul 3, 2018, at 1:11 PM, Marcus wrote: > > Am 01.07.2018 um 17:27 schrieb Peter Kovacs: >> I would like to bring a 4.1.6 Release on the way in July. Even if we manage >> to get 4.2.0 re

Re: A 4.1.6 Release

2018-07-03 Thread Marcus
Am 01.07.2018 um 17:27 schrieb Peter Kovacs: I would like to bring a 4.1.6 Release on the way in July. Even if we manage to get 4.2.0 ready it will only be a beta. And we have some stuff to get out to the people. Matthias has created a suggestion for a 4.1.6 release on security. Containing

Re: A 4.1.6 Release

2018-07-03 Thread Matthias Seidel
Hi Peter, Am 01.07.2018 um 17:27 schrieb Peter Kovacs: > Hi everbody. > > > I would like to bring a 4.1.6 Release on the way in July. Even if we > manage to get 4.2.0 ready it will only be a beta. And we have some > stuff to get out to the people. > > Matthias has created

Re: A 4.1.6 Release

2018-07-02 Thread Keith N. McKenna
On 7/1/2018 11:27 AM, Peter Kovacs wrote: > Hi everbody. > > > I would like to bring a 4.1.6 Release on the way in July. Even if we > manage to get 4.2.0 ready it will only be a beta. And we have some stuff > to get out to the people. > > Matthias has created a suggestio

Re: A 4.1.6 Release

2018-07-02 Thread Carl Marcum
Hi Peter, On 07/01/2018 11:27 AM, Peter Kovacs wrote: Hi everbody. I would like to bring a 4.1.6 Release on the way in July. Even if we manage to get 4.2.0 ready it will only be a beta. And we have some stuff to get out to the people. Matthias has created a suggestion for a 4.1.6 release

Re: A 4.1.6 Release

2018-07-02 Thread Jim Jagielski
Works for me... > On Jul 1, 2018, at 11:27 AM, Peter Kovacs wrote: > > Hi everbody. > > > I would like to bring a 4.1.6 Release on the way in July. Even if we manage > to get 4.2.0 ready it will only be a beta. And we have some stuff to get out > to the people. >

Re: A 4.1.6 Release

2018-07-02 Thread Peter Kovacs
, Peter Kovacs wrote: Hi everbody. I would like to bring a 4.1.6 Release on the way in July. Even if we manage to get 4.2.0 ready it will only be a beta. And we have some stuff to get out to the people. Matthias has created a suggestion for a 4.1.6 release on security. Containing some security

Re: A 4.1.6 Release

2018-07-01 Thread Kay Schenk
4.1.6 still be using gstreamer 0.10? On 07/01/2018 08:27 AM, Peter Kovacs wrote: > Hi everbody. > > > I would like to bring a 4.1.6 Release on the way in July. Even if we > manage to get 4.2.0 ready it will only be a beta. And we have some > stuff to get out to the people. > >

A 4.1.6 Release

2018-07-01 Thread Peter Kovacs
Hi everbody. I would like to bring a 4.1.6 Release on the way in July. Even if we manage to get 4.2.0 ready it will only be a beta. And we have some stuff to get out to the people. Matthias has created a suggestion for a 4.1.6 release on security. Containing some security fixes, plus