Hi,
Shaun McDonald wrote:
On 20 Mar 2007, at 00:00, :murb: (maarten brouwers) wrote:
http://website.openoffice.org/tryouts/murb/other/helptesting.gif
Hmm - why not an equally sized/shaped download button for the RCs/devel
versions as we have for the stable one?
Because I don't want the RC-download to interfere with the regular
downloads. Downloading the stable version should be a no-brainer for
everybody. Therefore a completely different format.
It is always very easy to forget about the ordinary user. Think about
your granny, or mother (depending on the generation that you come from)
and see whether they can manage to download and install ooo. To head to
the other extreme, you should be able to take a young child, (around the
age of 7-10) and they should be to install a bit of software like ooo.
I see the risk of confusion and agree that we should please our mothers.
But at the moment we (almost) totally ignore our siblings interested in
more than just the boring stable build (sorry for disfiguring the picture).
Back btw on the issue raised by Stefan, I am not sure whether it is wise
to make the banner too general. It think it is better to use it only
every now and then (for a month or so), or else the impact might
reduce to
0, not sure though...
A banner for RC builds should only be available while an RC is in the
process of being tested. In theory RC builds should be more stable/less
likely to have issues, than Milestone builds.
As I tried to explain we then would need two "banners" pointing to the
download/680 page - one during a RC phase and another for the regular
milestone phase. There is always a RC and/or milestone build available
in parallel to the stable build. So from my POV we could encourage
download/usage/testing of those at any time.
We could communicate however to those who are willing to download the RC
that there are test builds available all the time, and that there
continuous feedback is always appreciated. Maybe this would need for a
different 'contribute' text for RC-downloaders.
Milestone builds are the regular builds with the latest bug fixes. These
too should be advertised, especially for QA and those submitting bugs.
Many other projects ask you to check the latest build to see if that
still has the bug before submitting the bug. To reduce the likelihood of
stoppers showing up in the RC builds, we need more people using and
reporting issues with these builds.
Exactly! That's one of the requests in Martin's initial message which
triggered the discussion. I'm happy to give Maarten's sidebanner a try.
But I think we should promote developer builds at almost the same level
as stable builds. For me this means we should have two buttons which
guide to the downloads of stable/final/production vs.
developer/snapshot/milestone builds.
Greetings
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
