Re: Create tag for 4.2.0 Developer Build 1?
Hi. I finally got around to checking out rev. 1896514 from: http://home.apache.org/~jim/AOO-builds/ (last update 04/04/2019) So far so good. I will check if some of the extensions I use will work with this build. "Less is more." Kay On 3/27/19 9:33 AM, Jim Jagielski wrote: 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/repos/dist/dev/openoffice/4.2.0-Dev1/ Regards, Matthias Am 27.03.19 um 12:22 schrieb Jim Jagielski: 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: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - 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?)
Am 27.03.19 um 17:46 schrieb Dave Fisher: > >> On Mar 27, 2019, at 9:44 AM, Matthias Seidel >> wrote: >> >> Hi Dave, >> >> Am 27.03.19 um 17:37 schrieb Dave Fisher: >>> 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 >> That said, we are not going to *release* a Developer Build but we are >> going to make it available... ;-) >> >> Uploads will go to the /dev area. > Always good to check ;-) Definitely! However, the tag ends up as a "release" on GitHub [1]. But Infra is aware of that: https://issues.apache.org/jira/browse/LEGAL-438 [1] https://github.com/apache/openoffice/releases > On Mar 27, 2019, at 9:33 AM, Jim Jagielski wrote: 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/repos/dist/dev/openoffice/4.2.0-Dev1/ > > Regards, > > Matthias > > Am 27.03.19 um 12:22 schrieb Jim Jagielski: >> 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: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Create tag for 4.2.0 Developer Build 1? (was: Time for our first 4.2.0 beta?)
> On Mar 27, 2019, at 9:44 AM, Matthias Seidel > wrote: > > Hi Dave, > > Am 27.03.19 um 17:37 schrieb Dave Fisher: >> 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 > > That said, we are not going to *release* a Developer Build but we are > going to make it available... ;-) > > Uploads will go to the /dev area. Always good to check ;-) > >> >>> On Mar 27, 2019, at 9:33 AM, Jim Jagielski wrote: >>> >>> 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/repos/dist/dev/openoffice/4.2.0-Dev1/ Regards, Matthias Am 27.03.19 um 12:22 schrieb Jim Jagielski: > 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: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> > - 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 Dave, Am 27.03.19 um 17:37 schrieb Dave Fisher: > 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 That said, we are not going to *release* a Developer Build but we are going to make it available... ;-) Uploads will go to the /dev area. > >> On Mar 27, 2019, at 9:33 AM, Jim Jagielski wrote: >> >> 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/repos/dist/dev/openoffice/4.2.0-Dev1/ >>> >>> Regards, >>> >>> Matthias >>> >>> Am 27.03.19 um 12:22 schrieb Jim Jagielski: 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: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org >>> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Create tag for 4.2.0 Developer Build 1? (was: Time for our first 4.2.0 beta?)
Am 27.03.19 um 17:33 schrieb Jim Jagielski: > Is Infra aware of this upcoming "developer's" release? The procedure is the same like for Release Candidates... And even for releases: Infra said they don't need to be informed (because AOO isn't mirrored anymore?) See: https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.6 > >> 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/repos/dist/dev/openoffice/4.2.0-Dev1/ >> >> Regards, >> >>Matthias >> >> Am 27.03.19 um 12:22 schrieb Jim Jagielski: >>> 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: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> >> > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
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 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/repos/dist/dev/openoffice/4.2.0-Dev1/ >> >> Regards, >> >> Matthias >> >> Am 27.03.19 um 12:22 schrieb Jim Jagielski: >>> 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: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> >> >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - 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?)
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/repos/dist/dev/openoffice/4.2.0-Dev1/ > > Regards, > >Matthias > > Am 27.03.19 um 12:22 schrieb Jim Jagielski: >> 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: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> > > - 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?)
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 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: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
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. - 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?)
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: 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-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
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?)
+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 > >> >> 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) and we still miss macOS there. >>> >>> As soon as the Release Manager creates a tag I can begin to build for >>> Windows. (Remember, it takes about 15 hours for a complete build incl. >>> all languages, SDK and Language Packs). Revision 1856225 would be OK >>> for me. >>> >>> Dev1 will still contain many things to be fixed. But it can be a common >>> base to discuss about. And of course more Developer Builds are likely >>> to >>> follow until we reach the level for a (public) Beta. >>> >>> Does that sound like a way to go? >>> >>> Regards, >>> >>>Matthias >>> >>> >>> Am 24.03.19 um 16:39 schrieb Matthias Seidel: 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.0 what is >>> in >>> the scope, and what is not. >> Users should not expect anything, this is for developers. > We want to write a blog post for developers? We want to release a *developer build* right now and that is what we should announce (when it is ready): What it is intended for, what known bugs are still in it and need to >>> be fixed, how the translation process is proceeding. Call for testing, etc... This can be announced on dev@, dev-de@, l10n@ and the forum. Also >>> this should be linked on our homepage to give the average user an >>> impression about our latest development activities. Regards, Matthias P.S.: Of course we can (and should) do much more blogposts in >>> general. ;-) >>> 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, which we want to make and >>> finish >>> with the release criteria. >> Beta has no state at the moment. > Sorry, was not good at expressing. I mean we should say which >>> conditions > have to be met in order to start into Beta Phase, and to whom it is > interesting. >>> That would make it for me worthwhile to give people a frame for >>> the >>> 4.2.0 development line and to write about. >>> >>> Right? Or what do you believe we should write in the Blog post? >> I would be happy if we only had a page (in CWiki?) to work together >>> on >> the blogpost... >> >> Or did you want to do it all alone? ;-) > No I just think we have a total different idea what this blog post > should contain. Okay, I will reduce my writings to amore overview >>> level > and then post. >> Matthias >> >>> On 24.03.19 13:09, Matthias Seidel wrote: 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... > 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 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! ;-) >> >> Matthias >> >>> 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 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] >>> https://dist.apache.org/repos/dist/dev/openoffice/4.2.0
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 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. (Remember, it takes about 15 hours for a complete build incl. >> all languages, SDK and Language Packs). Revision 1856225 would be OK >> for me. >> >> Dev1 will still contain many things to be fixed. But it can be a common >> base to discuss about. And of course more Developer Builds are likely >> to >> follow until we reach the level for a (public) Beta. >> >> Does that sound like a way to go? >> >> Regards, >> >> Matthias >> >> >> Am 24.03.19 um 16:39 schrieb Matthias Seidel: >>> 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.0 what is >> in >> the scope, and what is not. > Users should not expect anything, this is for developers. We want to write a blog post for developers? >>> We want to release a *developer build* right now and that is what we >>> should announce (when it is ready): >>> What it is intended for, what known bugs are still in it and need to >> be >>> fixed, how the translation process is proceeding. >>> Call for testing, etc... >>> >>> This can be announced on dev@, dev-de@, l10n@ and the forum. Also >> this >>> should be linked on our homepage to give the average user an >> impression >>> about our latest development activities. >>> >>> Regards, >>> >>> Matthias >>> >>> P.S.: Of course we can (and should) do much more blogposts in >> general. ;-) >> 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, which we want to make and >> finish >> with the release criteria. > Beta has no state at the moment. Sorry, was not good at expressing. I mean we should say which >> conditions have to be met in order to start into Beta Phase, and to whom it is interesting. >> That would make it for me worthwhile to give people a frame for >> the >> 4.2.0 development line and to write about. >> >> Right? Or what do you believe we should write in the Blog post? > I would be happy if we only had a page (in CWiki?) to work together >> on > the blogpost... > > Or did you want to do it all alone? ;-) No I just think we have a total different idea what this blog post should contain. Okay, I will reduce my writings to amore overview >> level and then post. > Matthias > >> On 24.03.19 13:09, Matthias Seidel wrote: >>> 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... 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 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! ;-) > > Matthias > >> 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 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] >> https://dist.apache.org/repos/dist/dev/openoffice/4.2.0-Dev1/ >>> >>> Am 21.03.19 um 21:10 schrieb Peter Kovacs: +1, I will create a subspapge and Link it. On 21.03.19 16:19, Matthias Seidel wrote: > Hi Peter, > > +1 > >
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) and we still miss macOS there. > >As soon as the Release Manager creates a tag I can begin to build for >Windows. (Remember, it takes about 15 hours for a complete build incl. >all languages, SDK and Language Packs). Revision 1856225 would be OK >for me. > >Dev1 will still contain many things to be fixed. But it can be a common >base to discuss about. And of course more Developer Builds are likely >to >follow until we reach the level for a (public) Beta. > >Does that sound like a way to go? > >Regards, > > Matthias > > >Am 24.03.19 um 16:39 schrieb Matthias Seidel: >> 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.0 what is >in > the scope, and what is not. Users should not expect anything, this is for developers. >>> We want to write a blog post for developers? >> We want to release a *developer build* right now and that is what we >> should announce (when it is ready): >> What it is intended for, what known bugs are still in it and need to >be >> fixed, how the translation process is proceeding. >> Call for testing, etc... >> >> This can be announced on dev@, dev-de@, l10n@ and the forum. Also >this >> should be linked on our homepage to give the average user an >impression >> about our latest development activities. >> >> Regards, >> >> Matthias >> >> P.S.: Of course we can (and should) do much more blogposts in >general. ;-) >> > 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, which we want to make and >finish > with the release criteria. Beta has no state at the moment. >>> Sorry, was not good at expressing. I mean we should say which >conditions >>> have to be met in order to start into Beta Phase, and to whom it is >>> interesting. > That would make it for me worthwhile to give people a frame for >the > 4.2.0 development line and to write about. > > Right? Or what do you believe we should write in the Blog post? I would be happy if we only had a page (in CWiki?) to work together >on the blogpost... Or did you want to do it all alone? ;-) >>> No I just think we have a total different idea what this blog post >>> should contain. Okay, I will reduce my writings to amore overview >level >>> and then post. Matthias > On 24.03.19 13:09, Matthias Seidel wrote: >> 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... >> >>> 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 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! ;-) Matthias > 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 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] >https://dist.apache.org/repos/dist/dev/openoffice/4.2.0-Dev1/ >> >> >> Am 21.03.19 um 21:10 schrieb Peter Kovacs: >>> +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 Peter Kovacs: > Lets
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. (Remember, it takes about 15 hours for a complete build incl. all languages, SDK and Language Packs). Revision 1856225 would be OK for me. Dev1 will still contain many things to be fixed. But it can be a common base to discuss about. And of course more Developer Builds are likely to follow until we reach the level for a (public) Beta. Does that sound like a way to go? Regards, Matthias Am 24.03.19 um 16:39 schrieb Matthias Seidel: > 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.0 what is in the scope, and what is not. >>> Users should not expect anything, this is for developers. >> We want to write a blog post for developers? > We want to release a *developer build* right now and that is what we > should announce (when it is ready): > What it is intended for, what known bugs are still in it and need to be > fixed, how the translation process is proceeding. > Call for testing, etc... > > This can be announced on dev@, dev-de@, l10n@ and the forum. Also this > should be linked on our homepage to give the average user an impression > about our latest development activities. > > Regards, > > Matthias > > P.S.: Of course we can (and should) do much more blogposts in general. ;-) > 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, which we want to make and finish with the release criteria. >>> Beta has no state at the moment. >> Sorry, was not good at expressing. I mean we should say which conditions >> have to be met in order to start into Beta Phase, and to whom it is >> interesting. That would make it for me worthwhile to give people a frame for the 4.2.0 development line and to write about. Right? Or what do you believe we should write in the Blog post? >>> I would be happy if we only had a page (in CWiki?) to work together on >>> the blogpost... >>> >>> Or did you want to do it all alone? ;-) >> No I just think we have a total different idea what this blog post >> should contain. Okay, I will reduce my writings to amore overview level >> and then post. >>> Matthias >>> On 24.03.19 13:09, Matthias Seidel wrote: > 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... > >> 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 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! ;-) >>> >>> Matthias >>> 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 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] https://dist.apache.org/repos/dist/dev/openoffice/4.2.0-Dev1/ > > > Am 21.03.19 um 21:10 schrieb Peter Kovacs: >> +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 Peter Kovacs: 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 >
