+1 And thanks to Matthias for his work. Mechtilde
Am 26. März 2019 10:44:01 MEZ schrieb Matthias Seidel <matthias.sei...@hamburg.de>: >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.... >>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Mar 19, 2019, at 3:04 PM, Matthias Seidel ><matthias.sei...@hamburg.de> 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? ;-) >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >--------------------------------------------------------------------- >>>>>>>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >--------------------------------------------------------------------- >>>>>>>>> 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 >>> >>>
