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 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.)
- prepare the install files as a normal release but with special file names
- no participation with the update service
- upload the install files to SourceForge in an own subdir
- offer them on our download webpage
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
