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 build input. Feedback in languages other
than English could be gathered on the appropriate forums, though they may
need to make a dedicated area. It would be nice to widen the range of
participants beyond people comfortable in English.
thanks for your input.
I am not sure what the concern is behind the comment "What I mean is, is
there enough coverage of moderators and power users?". On the en forum we
When we tell the people "Please visit our forums when you have problems
or feedback for improvements" there should be enough people for coverage
to collect that feedback. It would be too bad when the users don't get
feedback or way too late. ;-)
have close to 24 hour coverage of moderators and volunteers and I don't
think an increase in traffic from a beta build would be a problem. The es
forum is the only other one I have experience with and I think there are
plenty of moderators and volunteers there to handle an increase in traffic,
though I obviously have not asked them about this.
OK, that sounds good. In the worst case the en forums in an special Beta
release area could take some more languages - of course only as exception.
I would be happy to make note on this list of interesting or repeated input
about a beta build appearing on the en or es forums.
At the moment we are just discussing what is possible to decide later
what to do.
Stating the correct way to give feedback on the Splash screen should be
considered.
The splash screen is not the best place as it's shown too short. ;-)
That was my mistake.
But the About box, download webpage, release announcement, release
notes, blog post are way better to tell the people what to expect and
where to go.
Marcus
On Mon, Jan 28, 2019 at 12:53 PM Marcus <marcus.m...@wtnet.de> wrote:
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
