Time for our first 4.2.0 beta?

I think we are at a stage where we should consider doing our 1st beta release of 4.2.0... we have successful builds for macOS, Linux 32 and 64, and Windows; we have a stable 4.2.0-dev branch, and enough changes to warrant a beta release for testing and feedback (all IMO ;) ). Any comments or other

Re: Time for our first 4.2.0 beta?

Hello Jim, the beta version should contain the recent translation, so I will start to prepare an update of the *.sdf files. Kind regards Am 28.01.19 um 14:20 schrieb Jim Jagielski: > I think we are at a stage where we should consider doing our > 1st beta release of 4.2.0... we have successful bu

Re: Time for our first 4.2.0 beta?

Perfect, thx. Just so I know, what's the procedure for us doing beta releases? Where do they go? > On Jan 28, 2019, at 12:31 PM, Mechtilde wrote: > > Hello Jim, > > the beta version should contain the recent translation, so I will start > to prepare an update of the *.sdf files. > > Kind reg

Re: Time for our first 4.2.0 beta?

Am 28.01.19 um 19:39 schrieb Jim Jagielski: Perfect, thx. Just so I know, what's the procedure for us doing beta releases? Where do they go? this will be our first beta release here at Apache. So, nobody can tell you what to do / where to go and we have to find the way together. ;-) I woul

Re: Time for our first 4.2.0 beta?

Hi Marcus, Am 28.01.19 um 20:30 schrieb Marcus: > Am 28.01.19 um 19:39 schrieb Jim Jagielski: >> Perfect, thx. >> >> Just so I know, what's the procedure for us doing beta releases? >> Where do they go? > > this will be our first beta release here at Apache. So, nobody can > tell you what to do /

Re: Time for our first 4.2.0 beta?

Hi Jim, Am 28.01.19 um 19:39 schrieb Jim Jagielski: > Perfect, thx. > > Just so I know, what's the procedure for us doing beta releases? Where do > they go? Just a general reminder: A bunch of people, including Mechtilde, Andrea and me will be at FOSDEM in Brussels next weekend. I have some la

Re: Time for our first 4.2.0 beta?

Am 28.01.19 um 21:06 schrieb Matthias Seidel: Am 28.01.19 um 20:30 schrieb Marcus: Am 28.01.19 um 19:39 schrieb Jim Jagielski: Perfect, thx. Just so I know, what's the procedure for us doing beta releases? Where do they go? this will be our first beta release here at Apache. So, nobody can t

Re: Time for our first 4.2.0 beta?

Am 28.01.19 um 21:23 schrieb Marcus: > Am 28.01.19 um 21:06 schrieb Matthias Seidel: >> Am 28.01.19 um 20:30 schrieb Marcus: >>> Am 28.01.19 um 19:39 schrieb Jim Jagielski: Perfect, thx. Just so I know, what's the procedure for us doing beta releases? Where do they go? >>> >>> t

Re: Time for our first 4.2.0 beta?

I am a moderator on the en forum but I am speaking only for myself here. I think gathering feedback on the forum would be a good solution. The en forum has a User Experience area that gets very little traffic and could perhaps be used to gather beta build input. Feedback in languages other than Eng

Re: Time for our first 4.2.0 beta?

On 28.01.19 21:32, Matthias Seidel wrote: > > Personally, I don't think we are at Beta stage already... But we > definitely have to work towards it! ;-) > > Matthias What is missing? I am happy on the progress. - To unsubscr

Re: Time for our first 4.2.0 beta?

Am 28.01.19 um 23:20 schrieb Peter Kovacs: > On 28.01.19 21:32, Matthias Seidel wrote: >> Personally, I don't think we are at Beta stage already... But we >> definitely have to work towards it! ;-) >> >> Matthias > > What is missing? I can simply crash it with two clicks... ;-) That bug is 4 1/2

Re: Time for our first 4.2.0 beta?

Am 28.01.19 um 21:32 schrieb Matthias Seidel: Am 28.01.19 um 21:23 schrieb Marcus: Am 28.01.19 um 21:06 schrieb Matthias Seidel: Am 28.01.19 um 20:30 schrieb Marcus: Am 28.01.19 um 19:39 schrieb Jim Jagielski: Perfect, thx. Just so I know, what's the procedure for us doing beta releases? Whe

Re: Time for our first 4.2.0 beta?

Hi Marcus, Am 28.01.19 um 23:52 schrieb Marcus: > Am 28.01.19 um 21:32 schrieb Matthias Seidel: >> Am 28.01.19 um 21:23 schrieb Marcus: >>> Am 28.01.19 um 21:06 schrieb Matthias Seidel: Am 28.01.19 um 20:30 schrieb Marcus: > Am 28.01.19 um 19:39 schrieb Jim Jagielski: >> Perfect, thx.

Re: Time for our first 4.2.0 beta?

Hi Jim, all > I think we are at a stage where we should consider doing our > 1st beta release of 4.2.0... we have successful builds for macOS, > Linux 32 and 64, and Windows; we have a stable 4.2.0-dev branch, > and enough changes to warrant a beta release for testing and > fe

Re: Time for our first 4.2.0 beta?

Am 29.01.19 um 13:52 schrieb Matthias Seidel: Hi Jim, Am 29.01.19 um 13:28 schrieb Jim Jagielski: On Jan 28, 2019, at 3:23 PM, Marcus > wrote: Am 28.01.19 um 21:06 schrieb Matthias Seidel: Am 28.01.19 um 20:30 schrieb Marcus: Am 28.01.19 um 19:39 schrieb Jim J

Re: Time for our first 4.2.0 beta?

Am 29.01.19 um 13:05 schrieb Pedro Lino: I think we are at a stage where we should consider doing our 1st beta release of 4.2.0... we have successful builds for macOS, Linux 32 and 64, and Windows; we have a stable 4.2.0-dev branch, and enough changes to warrant a beta relea

Re: Time for our first 4.2.0 beta?

Am 29.01.19 um 20:14 schrieb Marcus: > Am 29.01.19 um 13:52 schrieb Matthias Seidel: >> Hi Jim, >> >> Am 29.01.19 um 13:28 schrieb Jim Jagielski: >>> >>> On Jan 28, 2019, at 3:23 PM, Marcus >>> > wrote: Am 28.01.19 um 21:06 schrieb Matthias Seidel: >

Re: Time for our first 4.2.0 beta?

Am 28.01.19 um 21:58 schrieb F C. Costero: I am a moderator on the en forum but I am speaking only for myself here. I think gathering feedback on the forum would be a good solution. The en forum has a User Experience area that gets very little traffic and could perhaps be used to gather beta buil

Re: Time for our first 4.2.0 beta?

> On January 29, 2019 at 7:21 PM Marcus wrote: > Am 29.01.19 um 13:05 schrieb Pedro Lino: > > Shouldn't AOO be concerned that previous users are not notified of new > > releases > > (or extension updates)? The update notification mechanism has been broken > > for months. This means that user

Re: Time for our first 4.2.0 beta?

Am 29.01.19 um 21:53 schrieb Pedro Lino: >> On January 29, 2019 at 7:21 PM Marcus wrote: >> Am 29.01.19 um 13:05 schrieb Pedro Lino: >>> Shouldn't AOO be concerned that previous users are not notified of new >>> releases >>> (or extension updates)? The update notification mechanism has been broke

Re: Time for our first 4.2.0 beta?

> On January 29, 2019 at 9:02 PM Matthias Seidel < > matthias.sei...@hamburg.de mailto:matthias.sei...@hamburg.de > wrote: > > > > How is this related to 4.2.0 Beta?! > The subject of this email/topic is "Time for our first 4.2.0 beta?" M

Re: Time for our first 4.2.0 beta?

Am 29.01.19 um 22:57 schrieb Pedro Lino: On January 29, 2019 at 9:02 PM Matthias Seidel < matthias.sei...@hamburg.de mailto:matthias.sei...@hamburg.de > wrote: How is this related to 4.2.0 Beta?! The subject of this email/topic is "Time for our first 4.2.0 beta?"

Re: Time for our first 4.2.0 beta?

> On Jan 29, 2019, at 7:52 AM, Matthias Seidel > wrote: > > Do you also build SDK and language pack as beta? See: > > I do yes... my build scripts (see https://svn.apache.org/repos/asf/openoffice/devtools/build-scripts/4.2.0-dev) have a '--beta' option that builds all the related Beta arti

Re: Time for our first 4.2.0 beta?

Am 30.01.19 um 14:24 schrieb Jim Jagielski: sorry to ask, do you have also a screenshot for the About box? Sure, no prob: thanks It seems that the space is nearly full and we shouldn't squeeze much more text into it. What about a short sentence + link to a new webpage that gives more i

Re: Time for our first 4.2.0 beta?

Hi Jim, Am 30.01.19 um 16:15 schrieb Jim Jagielski: > >> On Jan 29, 2019, at 7:52 AM, Matthias Seidel >> wrote: >> >> Do you also build SDK and language pack as beta? See: >> >> > I do yes... my build scripts (see > https://svn.apache.org/repos/asf/openoffice/devtools/build-scripts/4.2.0-dev) >

Re: Time for our first 4.2.0 beta?

On January 29, 2019 at 9:02 PM Matthias Seidel < >>> matthias.sei...@hamburg.de mailto:matthias.sei...@hamburg.de > wrote: >> >>> How is this related to 4.2.0 Beta?! >> >> The subject of this email/topic is "Time for our first 4.2.0 beta?&quo

Re: Time for our first 4.2.0 beta?

On 30/01/2019 Peter Kovacs wrote: AFAIK Root cause is that the TLS connection can not be established in Version 1.2 due to wrong version on client side. The Idea has been to lower security on server back to 1.1 Version for now. I confirm this is the conclusion we reached, but then we (at least

Re: Time for our first 4.2.0 beta?

Am 31.01.19 um 23:33 schrieb Andrea Pescetti: > On 30/01/2019 Peter Kovacs wrote: >> AFAIK Root cause is that the TLS connection can not be established in >> Version 1.2 due to wrong version on client side. >> The Idea has been to lower security on server back to 1.1 Version for >> now. > > I confi

Re: Time for our first 4.2.0 beta?

Hi Matthias, Andrea, all > On January 31, 2019 at 11:08 PM Matthias Seidel < > matthias.sei...@hamburg.de mailto:matthias.sei...@hamburg.de > wrote: > > > Am 31.01.19 um 23:33 schrieb Andrea Pescetti: > > > > On 30/01/2019 Peter Kovacs wrote: > > > > > > >

Re: Time for our first 4.2.0 beta?

Time for another ping... what does everyone think? Time? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Time for our first 4.2.0 beta?

Just in case, I'm doing Beta builds of AOO42X (HEAD) for macOS and Linux 64+32 > On Feb 14, 2019, at 11:45 AM, Jim Jagielski wrote: > > Time for another ping... what does everyone think? Time? > > - > To unsubscribe, e-mail: de

Re: Time for our first 4.2.0 beta?

Great! Please post the URL of the binaries so other people can start testing. On 02/14/2019 11:29 AM, Jim Jagielski wrote: Just in case, I'm doing Beta builds of AOO42X (HEAD) for macOS and Linux 64+32 On Feb 14, 2019, at 11:45 AM, Jim Jagielski wrote: Time for another ping... what does ev

Re: Time for our first 4.2.0 beta?

Am 14.02.19 um 19:39 schrieb JD: Great! Please post the URL of the binaries so other people can start testing. this is the keyword: First we need to do some tests on our own. Otherwise we risk to release a beta that doesn't survive barley longer than a small smoketest. The problem is that d

Re: Time for our first 4.2.0 beta?

Hi Jim, IMO, the situation hasn't changed so much. We should at least fix issue 125129 [1] before we release a (public) beta. I have seen that Damjan is investigating... Then we need time to inform translators on l10n@ before we can export the latest translations from Pootle. At the moment most

Re: Time for our first 4.2.0 beta?

Bug 125129 looks like a wild goose chase and requires considerable understanding of the framework layer, but I'll try continue when I have time. My own release checklist would include: 1. Library audit. 1.1 Did we lose or gain any public symbols in our libraries since the 4.1.0? Gbuild requires ex

Re: Time for our first 4.2.0 beta?

On Fri, 15 Feb 2019 11:55:32 +0200 Damjan Jovanovic wrote: > Bug 125129 looks like a wild goose chase and requires considerable > understanding of the framework layer, but I'll try continue when I have > time. A quick experiment with Writer in 4.2.0 shows me that one cannot insert a background

Re: Time for our first 4.2.0 beta?

> On February 14, 2019 at 4:45 PM Jim Jagielski wrote: > > > Time for another ping... what does everyone think? Time? How does a Beta version install on Linux?* Is it installed in parallel to the Stable version (like on Windows)? If not then I believe the update problem should be fixed *bef

Re: Time for our first 4.2.0 beta?

On Fri, 15 Feb 2019 10:56:25 + (WET) Pedro Lino wrote: > > > On February 14, 2019 at 4:45 PM Jim Jagielski wrote: > > > > > > Time for another ping... what does everyone think? Time? > > How does a Beta version install on Linux?* Is it installed in parallel to the > Stable version (like

Re: Time for our first 4.2.0 beta?

On 2/15/2019 6:03 AM, Rory O'Farrell wrote: > On Fri, 15 Feb 2019 10:56:25 + (WET) Pedro Lino > wrote: > >> >>> On February 14, 2019 at 4:45 PM Jim Jagielski >>> wrote: >>> >>> >>> Time for another ping... what does everyone think? Time? >> >> How does a Beta version install on Linux?* I

Re: Time for our first 4.2.0 beta?

Hi Rory, Keith, all > On February 15, 2019 at 11:32 AM "Keith N. McKenna" < > keith.mcke...@comcast.net mailto:keith.mcke...@comcast.net > wrote: > > > On 2/15/2019 6:03 AM, Rory O'Farrell wrote: > > > > On Fri, 15 Feb 2019 10:56:25 + (WET) Pedro Lino > > <

Re: Time for our first 4.2.0 beta?

Just trying to keep the momentum going ;) > On Feb 14, 2019, at 6:25 PM, Matthias Seidel > wrote: > > Hi Jim, > > IMO, the situation hasn't changed so much. > > We should at least fix issue 125129 [1] before we release a (public) > beta. I have seen that Damjan is investigating... > > Then w

Re: Time for our first 4.2.0 beta?

HEllo Pedro Am 15.02.19 um 11:56 schrieb Pedro Lino: > >> On February 14, 2019 at 4:45 PM Jim Jagielski wrote: >> >> >> Time for another ping... what does everyone think? Time? > > How does a Beta version install on Linux?* Is it installed in parallel to the > Stable version (like on Windows)?

Re: Time for our first 4.2.0 beta?

Hi Jim, Am 15.02.19 um 13:33 schrieb Jim Jagielski: > Just trying to keep the momentum going ;) Definitely! And I would be the last person not wanting to release AOO 4.2.0 (beta)! ;-) Regards,    Matthias > >> On Feb 14, 2019, at 6:25 PM, Matthias Seidel >> wrote: >> >> Hi Jim, >> >> IMO, t

Re: Time for our first 4.2.0 beta?

Release, as in GA, or release as in Beta? > On Feb 15, 2019, at 4:55 AM, Damjan Jovanovic wrote: > > Bug 125129 looks like a wild goose chase and requires considerable > understanding of the framework layer, but I'll try continue when I have > time. > > My own release checklist would include: >

Re: Time for our first 4.2.0 beta?

Hi Rory, Am 15.02.19 um 11:22 schrieb Rory O'Farrell: > On Fri, 15 Feb 2019 11:55:32 +0200 > Damjan Jovanovic wrote: > >> Bug 125129 looks like a wild goose chase and requires considerable >> understanding of the framework layer, but I'll try continue when I have >> time. > A quick experiment wit

Re: Time for our first 4.2.0 beta?

On Mon, 18 Feb 2019 16:00:20 +0100 Matthias Seidel wrote: > Hi Rory, > > Am 15.02.19 um 11:22 schrieb Rory O'Farrell: > > On Fri, 15 Feb 2019 11:55:32 +0200 > > Damjan Jovanovic wrote: > > > >> Bug 125129 looks like a wild goose chase and requires considerable > >> understanding of the framewor

Re: Time for our first 4.2.0 beta?

On Mon, 18 Feb 2019 15:08:09 + Rory O'Farrell wrote: > On Mon, 18 Feb 2019 16:00:20 +0100 > Matthias Seidel wrote: > > > Hi Rory, > > > > Am 15.02.19 um 11:22 schrieb Rory O'Farrell: > > > On Fri, 15 Feb 2019 11:55:32 +0200 > > > Damjan Jovanovic wrote: > > > > > >> Bug 125129 looks like

Re: Time for our first 4.2.0 beta?

Hi Rory, Am 18.02.19 um 16:53 schrieb Rory O'Farrell: > On Mon, 18 Feb 2019 15:08:09 + > Rory O'Farrell wrote: > >> On Mon, 18 Feb 2019 16:00:20 +0100 >> Matthias Seidel wrote: >> >>> Hi Rory, >>> >>> Am 15.02.19 um 11:22 schrieb Rory O'Farrell: On Fri, 15 Feb 2019 11:55:32 +0200 D

Re: Time for our first 4.2.0 beta?

On Mon, 18 Feb 2019 16:58:38 +0100 Matthias Seidel wrote: > Hi Rory, > > Am 18.02.19 um 16:53 schrieb Rory O'Farrell: > > On Mon, 18 Feb 2019 15:08:09 + > > Rory O'Farrell wrote: > > > >> On Mon, 18 Feb 2019 16:00:20 +0100 > >> Matthias Seidel wrote: > >> > >>> Hi Rory, > >>> > >>> Am 15.0

Re: Time for our first 4.2.0 beta?

Hi Rory, Am 18.02.19 um 17:07 schrieb Rory O'Farrell: > On Mon, 18 Feb 2019 16:58:38 +0100 > Matthias Seidel wrote: > >> Hi Rory, >> >> Am 18.02.19 um 16:53 schrieb Rory O'Farrell: >>> On Mon, 18 Feb 2019 15:08:09 + >>> Rory O'Farrell wrote: >>> On Mon, 18 Feb 2019 16:00:20 +0100 M

Re: Time for our first 4.2.0 beta?

Hi Jim and all, As mentioned before, I think we need some more time before doing a (public) beta. But I also want to get a wider user base for testing and something "official" we can base our discussions on. So here is my proposal: We could create a tag (snapshot420 or whatever) and build it as

Re: Time for our first 4.2.0 beta?

Hi all! I am still open for input. Even if you are not involved in development/release, you sure have an opinion, don't you? ;-) Regards,    Matthias Am 24.02.19 um 17:35 schrieb Matthias Seidel: > Hi Jim and all, > > As mentioned before, I think we need some more time before doing a > (public

Re: Time for our first 4.2.0 beta?

On Thu, 7 Mar 2019 11:46:08 +0100 Matthias Seidel wrote: > Hi all! > > I am still open for input. > > Even if you are not involved in development/release, you sure have an > opinion, don't you? ;-) > > Regards, > >    Matthias I'm using 4.2.0, currently revision 1854799, for daily work on X

Re: Time for our first 4.2.0 beta?

++1 > On Feb 24, 2019, at 11:35 AM, Matthias Seidel > wrote: > > Hi Jim and all, > > As mentioned before, I think we need some more time before doing a > (public) beta. > But I also want to get a wider user base for testing and something > "official" we can base our discussions on. > > So her

Re: Time for our first 4.2.0 beta?

Hi - > On Mar 7, 2019, at 6:31 AM, Jim Jagielski wrote: > > ++1 > >> On Feb 24, 2019, at 11:35 AM, Matthias Seidel >> wrote: >> >> Hi Jim and all, >> >> As mentioned before, I think we need some more time before doing a >> (public) beta. >> But I also want to get a wider user base for testi

Re: Time for our first 4.2.0 beta?

On Thu, 7 Mar 2019 08:02:49 -0800 Dave Fisher wrote: > Hi - > > > On Mar 7, 2019, at 6:31 AM, Jim Jagielski wrote: > > > > ++1 > > > >> On Feb 24, 2019, at 11:35 AM, Matthias Seidel > >> wrote: > >> > >> Hi Jim and all, > >> > >> As mentioned before, I think we need some more time before

Re: Time for our first 4.2.0 beta?

Hi Dave, Am 07.03.19 um 17:02 schrieb Dave Fisher: > Hi - > >> On Mar 7, 2019, at 6:31 AM, Jim Jagielski wrote: >> >> ++1 >> >>> On Feb 24, 2019, at 11:35 AM, Matthias Seidel >>> wrote: >>> >>> Hi Jim and all, >>> >>> As mentioned before, I think we need some more time before doing a >>> (publi

Re: Time for our first 4.2.0 beta?

> On Mar 7, 2019, at 8:14 AM, Matthias Seidel > wrote: > > Hi Dave, > > Am 07.03.19 um 17:02 schrieb Dave Fisher: >> Hi - >> >>> On Mar 7, 2019, at 6:31 AM, Jim Jagielski wrote: >>> >>> ++1 >>> On Feb 24, 2019, at 11:35 AM, Matthias Seidel wrote: Hi Jim and all, >>>

Re: Time for our first 4.2.0 beta?

Am 07.03.19 um 17:02 schrieb Dave Fisher: On Mar 7, 2019, at 6:31 AM, Jim Jagielski wrote: ++1 On Feb 24, 2019, at 11:35 AM, Matthias Seidel wrote: As mentioned before, I think we need some more time before doing a (public) beta. But I also want to get a wider user base for testing and som

Re: Time for our first 4.2.0 beta?

Hi Marcus, Am 07.03.19 um 21:03 schrieb Marcus: > Am 07.03.19 um 17:02 schrieb Dave Fisher: >>> On Mar 7, 2019, at 6:31 AM, Jim Jagielski wrote: >>> >>> ++1 >>> On Feb 24, 2019, at 11:35 AM, Matthias Seidel wrote: As mentioned before, I think we need some more time before doi

Re: Time for our first 4.2.0 beta?

Am 08.03.19 um 17:01 schrieb Matthias Seidel: Am 07.03.19 um 21:03 schrieb Marcus: Am 07.03.19 um 17:02 schrieb Dave Fisher: On Mar 7, 2019, at 6:31 AM, Jim Jagielski wrote: ++1 On Feb 24, 2019, at 11:35 AM, Matthias Seidel wrote: As mentioned before, I think we need some more time before

Re: Time for our first 4.2.0 beta?

Hi Marcus, Am 08.03.19 um 18:31 schrieb Marcus: > Am 08.03.19 um 17:01 schrieb Matthias Seidel: >> Am 07.03.19 um 21:03 schrieb Marcus: >>> Am 07.03.19 um 17:02 schrieb Dave Fisher: > On Mar 7, 2019, at 6:31 AM, Jim Jagielski wrote: > > ++1 > >> On Feb 24, 2019, at 11:35 AM, M

Re: Time for our first 4.2.0 beta?

Hi Jim and all, Am 07.03.19 um 15:31 schrieb Jim Jagielski: > ++1 FYI: I just added a graphic for the about dialog which is now used when you build a Developer Snapshot: http://svn.apache.org/repos/asf/openoffice/trunk/main/ooo_custom_images/dev/introabout/about.png Additionally I will try to m

Re: Time for our first 4.2.0 beta?

Very cool. > On Mar 10, 2019, at 6:15 AM, Matthias Seidel > wrote: > > Hi Jim and all, > > Am 07.03.19 um 15:31 schrieb Jim Jagielski: >> ++1 > > FYI: > > I just added a graphic for the about dialog which is now used when you > build a Developer Snapshot: > http://svn.apache.org/repos/asf/op

Re: Time for our first 4.2.0 beta?

Let me know when you're done and I can fire up the "official" developer's builds :) > On Mar 11, 2019, at 10:13 AM, Jim Jagielski wrote: > > Very cool. > >> On Mar 10, 2019, at 6:15 AM, Matthias Seidel >> wrote: >> >> Hi Jim and all, >> >> Am 07.03.19 um 15:31 schrieb Jim Jagielski: >>> ++

Re: Time for our first 4.2.0 beta?

Hi Jim, Am 13.03.19 um 14:35 schrieb Jim Jagielski: > Let me know when you're done and I can fire up the "official" developer's > builds :) I just added the "Developer Snapshot" graphics for the Start Center. [1] My Windows test builds look good so far. BUT: Only recently I found out that on Win

Re: Time for our first 4.2.0 beta?

firing macOS up as we speak... > On Mar 14, 2019, at 10:34 AM, Matthias Seidel > wrote: > > Hi Jim, > > Am 13.03.19 um 14:35 schrieb Jim Jagielski: >> Let me know when you're done and I can fire up the "official" developer's >> builds :) > I just added the "Developer Snapshot" graphics for th

Re: Time for our first 4.2.0 beta?

I would agree that my pref would be for it to be much more similar in naming to our Beta. > On Mar 16, 2019, at 9:21 AM, Matthias Seidel > wrote: > > Hi Jim, > > Am 15.03.19 um 12:01 schrieb Jim Jagielski: >> I've upload just a couple of the macOS AOO-4.2.0-dev builds to: >> >> http://ho

Re: Time for our first 4.2.0 beta?

Hi Jim, Am 17.03.19 um 15:18 schrieb Jim Jagielski: > I would agree that my pref would be for it to be much more similar in naming > to our Beta. I am already preparing a commit that should fix it. ;-) In the future I would want to do Developer Builds much more often. The builds from our buildb

Re: Time for our first 4.2.0 beta?

Hi Jim, Am 17.03.19 um 15:18 schrieb Jim Jagielski: > I would agree that my pref would be for it to be much more similar in naming > to our Beta. https://svn.apache.org/viewvc?view=revision&revision=1855711 looks good to me. Windows binaries: https://home.apache.org/~mseidel/AOO-builds/AOO-420-

Re: Time for our first 4.2.0 beta?

I'm starting another macOS build. :) > On Mar 18, 2019, at 3:37 PM, Matthias Seidel > wrote: > > Hi Jim, > > Am 17.03.19 um 15:18 schrieb Jim Jagielski: >> I would agree that my pref would be for it to be much more similar in naming >> to our Beta. > > https://svn.apache.org/viewvc?view=revi

Re: Time for our first 4.2.0 beta?

Hi Jim, Am 19.03.19 um 14:51 schrieb Jim Jagielski: > I'm starting another macOS build. :) Great! If everything works as expected I plan to update the translation files (SDF) together with Mechtilde this week. Then we could tag/build Dev1 next weekend? Regards,    Matthias > >> On Mar 18, 201

Re: Time for our first 4.2.0 beta?

I agree that once we update the xlation files, we could be ready for a tag and build of Dev1 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Time for our first 4.2.0 beta?

Am 19.03.19 um 19:31 schrieb Jim Jagielski: > I agree that once we update the xlation files, we could be > ready for a tag and build of Dev1 Do we have volunteers to write a blog post? ;-) > > - > To unsubscribe, e-mail: dev-unsu

Re: Time for our first 4.2.0 beta?

If no one will, I will > On Mar 19, 2019, at 3:04 PM, Matthias Seidel > wrote: > > Am 19.03.19 um 19:31 schrieb Jim Jagielski: >> I agree that once we update the xlation files, we could be >> ready for a tag and build of Dev1 > > Do we have volunteers to write a blog post? ;-) > >> >> --

Re: Time for our first 4.2.0 beta?

Lets do this together, I write a first daraft on the weekend. And then we can add stuff. Okay? On 20.03.19 12:42, Jim Jagielski wrote: > If no one will, I will > >> On Mar 19, 2019, at 3:04 PM, Matthias Seidel >> wrote: >> >> Am 19.03.19 um 19:31 schrieb Jim Jagielski: >>> I agree that once

Re: Time for our first 4.2.0 beta?

+1! > On Mar 21, 2019, at 2:56 AM, Peter Kovacs wrote: > > Lets do this together, I write a first daraft on the weekend. And then > we can add stuff. > > Okay? > > On 20.03.19 12:42, Jim Jagielski wrote: >> If no one will, I will >> >>> On Mar 19, 2019, at 3:04 PM, Matthias Seidel >>> w

Re: Time for our first 4.2.0 beta?

Hi Peter, +1 How about crating the draft somewhere here: https://cwiki.apache.org/confluence/display/OOOUSERS/Apache+OpenOffice+4.2.0 Regards,    Matthias Am 21.03.19 um 07:56 schrieb Peter Kovacs: > Lets do this together, I write a first daraft on the weekend. And then > we can add stuff. > >

Re: Time for our first 4.2.0 beta?

+1, I will create a subspapge and Link it. On 21.03.19 16:19, Matthias Seidel wrote: > Hi Peter, > > +1 > > How about crating the draft somewhere here: > https://cwiki.apache.org/confluence/display/OOOUSERS/Apache+OpenOffice+4.2.0 > > Regards, > >    Matthias > > Am 21.03.19 um 07:56 schrieb Pete

Re: Time for our first 4.2.0 beta?

Hi all, Most of the translations for trunk and 42X are now updated. Some are still missing due to technical problems but as translation is a work in progress I think this will be sufficient for Dev1. I also created an empty directory structure on our dist server [1]. Regards,    Matthias [1] h

Re: Time for our first 4.2.0 beta?

Hi Matthias, Is there an overview on the Languages we have now available and which have Issues? All the Best Peter On 24.03.19 10:41, Matthias Seidel wrote: > Hi all, > > Most of the translations for trunk and 42X are now updated. Some are > still missing due to technical problems but as transl

Re: Time for our first 4.2.0 beta?

Hi Peter, Am 24.03.19 um 12:41 schrieb Peter Kovacs: > Hi Matthias, > > Is there an overview on the Languages we have now available and which > have Issues? Mechtilde knows best. But we should inform l10n@ about the languages where UI are not at 100% in Dev1. Let's start on the blogpost! ;-) M

Re: Time for our first 4.2.0 beta?

yes I am on it. I found 106 closed issues. Does this sound right, or should there be more? On 24.03.19 12:47, Matthias Seidel wrote: > Hi Peter, > > Am 24.03.19 um 12:41 schrieb Peter Kovacs: >> Hi Matthias, >> >> Is there an overview on the Languages we have now available and which >> have Issue

Re: Time for our first 4.2.0 beta?

Am 24.03.19 um 13:04 schrieb Peter Kovacs: > yes I am on it. I found 106 closed issues. Does this sound right, or > should there be more? I am not sure... But I am more interested in the open issues. And who fixes them! ;-) Remember, this is a developer build, not a Beta or even a release... >

Re: Time for our first 4.2.0 beta?

yes but we want to write a blog post on the Development Version. So I would like to write what the user can expect of 4.2.0 what is in the scope, and what is not. And then we need to describe how much bug fixes are in scope until beta, how many are optional. We should the describe the beta state

Re: Time for our first 4.2.0 beta?

Hi Peter, Am 24.03.19 um 13:37 schrieb Peter Kovacs: > yes but we want to write a blog post on the Development Version. > > So I would like to write what the user can expect of 4.2.0 what is in > the scope, and what is not. Users should not expect anything, this is for developers. > > And then we

Re: Time for our first 4.2.0 beta?

Hi Matthias, On 24.03.19 13:41, Matthias Seidel wrote: > Hi Peter, > > Am 24.03.19 um 13:37 schrieb Peter Kovacs: >> yes but we want to write a blog post on the Development Version. >> >> So I would like to write what the user can expect of 4.2.0 what is in >> the scope, and what is not. > Users s

Re: Time for our first 4.2.0 beta?

Okay I wrote the basics down: https://cwiki.apache.org/confluence/display/OOOUSERS/Blogpost Is this thedirection? On 24.03.19 14:23, Peter Kovacs wrote: > Hi Matthias, > > On 24.03.19 13:41, Matthias Seidel wrote: >> Hi Peter, >> >> Am 24.03.19 um 13:37 schrieb Peter Kovacs: >>> yes but we want

Re: Time for our first 4.2.0 beta?

Am 24.03.19 um 14:23 schrieb Peter Kovacs: > Hi Matthias, > > On 24.03.19 13:41, Matthias Seidel wrote: >> Hi Peter, >> >> Am 24.03.19 um 13:37 schrieb Peter Kovacs: >>> yes but we want to write a blog post on the Development Version. >>> >>> So I would like to write what the user can expect of 4.2

Create tag for 4.2.0 Developer Build 1? (was: Time for our first 4.2.0 beta?)

Hi all, I think it is time to move on and tag a Developer Snapshot (Dev1). People need something "official" to test. Our buildbots do not produce release quality (for various reasons) and we still miss macOS there. As soon as the Release Manager creates a tag I can begin to build for Windows. (Re

Re: Create tag for 4.2.0 Developer Build 1? (was: Time for our first 4.2.0 beta?)

+1 And thanks to Matthias for his work. Mechtilde Am 26. März 2019 10:44:01 MEZ schrieb Matthias Seidel : >Hi all, > >I think it is time to move on and tag a Developer Snapshot (Dev1). >People need something "official" to test. Our buildbots do not produce >release quality (for various reasons)

Re: Create tag for 4.2.0 Developer Build 1? (was: Time for our first 4.2.0 beta?)

Hi Mechtilde, Am 26.03.19 um 10:51 schrieb Stehmann: > +1 > And thanks to Matthias for his work. Without your work on the Pootle synchronization this wouldn't have been possible. ;-) Matthias > > Mechtilde > > Am 26. März 2019 10:44:01 MEZ schrieb Matthias Seidel > : >> Hi all, >> >> I think

Re: Create tag for 4.2.0 Developer Build 1? (was: Time for our first 4.2.0 beta?)

+1... kudos all around! > On Mar 26, 2019, at 5:59 AM, Matthias Seidel > wrote: > > Hi Mechtilde, > > Am 26.03.19 um 10:51 schrieb Stehmann: >> +1 >> And thanks to Matthias for his work. > > Without your work on the Pootle synchronization this wouldn't have been > possible. ;-) > > Matthias

Re: Create tag for 4.2.0 Developer Build 1? (was: Time for our first 4.2.0 beta?)

I'll be creating a tag today around 3pm EDT, unless I hear otherwise ;) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Create tag for 4.2.0 Developer Build 1? (was: Time for our first 4.2.0 beta?)

Hi Jim, Am 26.03.19 um 14:41 schrieb Jim Jagielski: > I'll be creating a tag today around 3pm EDT, unless I hear otherwise ;) Great! Did you enjoy the Apache Roadshow yesterday? ;-) Matthias > > - > To unsubscribe, e-mail: dev

Re: Create tag for 4.2.0 Developer Build 1? (was: Time for our first 4.2.0 beta?)

The TAG for the developer preview is now applied: https://svn.apache.org/repos/asf/openoffice/tags/AOO420-Dev-m1 I have started building Linux 64&32 and macOS previews based on that tag as we speak. - To unsubscribe, e-mail:

Re: Create tag for 4.2.0 Developer Build 1? (was: Time for our first 4.2.0 beta?)

> On Mar 26, 2019, at 9:48 AM, Matthias Seidel > wrote: > > Did you enjoy the Apache Roadshow yesterday? ;-) > I did actually... it's nice seeing smaller, more intimate events, esp located at colleges and universities. -

Re: Create tag for 4.2.0 Developer Build 1? (was: Time for our first 4.2.0 beta?)

I will start immediately with my Windows builds. Don't expect them before tomorrow evening... Upload directories exists here, rename if you like: https://dist.apache.org/repos/dist/dev/openoffice/4.2.0-Dev1/ Regards,    Matthias Am 27.03.19 um 12:22 schrieb Jim Jagielski: > The TAG for the deve

Re: Create tag for 4.2.0 Developer Build 1? (was: Time for our first 4.2.0 beta?)

Is Infra aware of this upcoming "developer's" release? > On Mar 27, 2019, at 12:17 PM, Matthias Seidel > wrote: > > I will start immediately with my Windows builds. Don't expect them > before tomorrow evening... > > Upload directories exists here, rename if you like: > https://dist.apache.org/

Re: Create tag for 4.2.0 Developer Build 1? (was: Time for our first 4.2.0 beta?)

Are we going to move this to /repos/dist/release/? That’s what they want the heads up about, correct? That way they can prevent thrashing between dist.a.o and archive.a.o > On Mar 27, 2019, at 9:33 AM, Jim Jagielski wrote: > > Is Infra aware of this upcoming "developer's" release? > >> On Mar

  1   2   >