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. >>>>>> >>>>>> 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. ;-) >>>> >>>> It is "our" second: ;-) >>>> >>>> https://archive.apache.org/dist/openoffice/4.1.0-beta/ >>> >>> OK, this is a bit embarrassing. ;-) >>> >>>>> I would say we should not do things different (at least not too many) >>>>> compared to our normal releases. >>>>> >>>>> After thinking a bit I suggest that we: >>>>> >>>>> - exchange the splash screen with a big and clear hint that it's a >>>>> beta (no production use, no regular support, etc.) >>> >>> When we had already a Beta release then this must be somewhere. >> >> See below. >> >> I already made an early test build for a Beta some time ago... > > sorry, actually I meant the about box. Do we have also for this a > special graphic and text content?
There are beta graphics [1] [2] [3] and the text can be changed via configure switch (as we do with our buildbots) As I wrote, the appropriate graphics are used by building the beta targets. Matthias [1] https://svn.apache.org/repos/asf/openoffice/branches/AOO42X/main/default_images/introabout/beta/about.png [2] https://svn.apache.org/repos/asf/openoffice/branches/AOO42X/main/default_images/introabout/beta/intro.png [3] https://svn.apache.org/repos/asf/openoffice/branches/AOO42X/main/default_images/framework/res/beta/backing.png > > Marcus > > > >>>>> - prepare the install files as a normal release but with special file >>>>> names >>>> A build with the special targets (openofficebeta, sdkoobeta, >>>> ooobetalanguagepack) will do this automatically. >>>>> - no participation with the update service >>>> >>>> --disable-online-update in configure. >>>> >>>>> - upload the install files to SourceForge in an own subdir >>>>> - offer them on our download webpage >>>> >>>> If the download page can handle that, it would be perfect. >>> >>> I think it's a matter of time to get this integrated. But should be >>> faster than the test phase for the Beta itself. >> >> Personally, I don't think we are at Beta stage already... But we >> definitely have to work towards it! ;-) >> >> Matthias >> >>> >>> Marcus >>> >>> >>> >>>>> I don't know how we can to collect the feedback. BZ is not the right >>>>> channel for this. Can we create a special beta area in the forums? >>>>> What I mean is, is there enough coverage of moderators and power >>>>> users? >>>>> >>>>> Marcus >>>>> >>>>> >>>>> >>>>>>> On Jan 28, 2019, at 12:31 PM, Mechtilde <o...@mechtilde.de> wrote: >>>>>>> >>>>>>> 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 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 thoughts? > > > --------------------------------------------------------------------- > 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
