Re: UK version of 3.3

Stuart Swales wrote:
> On 02/02/2011 17:05, Louis Su=E1rez-Potts wrote:
>> On 2011-02-02, at 11:05 , Marcus Lange wrote:
>>> Louis Su=E1rez-Potts wrote:
>>>> On 2011-02-02, at 10:35 , Stefan Taxhet (sonews) wrote:
>>>>> On 02.02.2011 16:25, Louis Su=E1rez-Potts wrote:
>>>>>> On 2011-02-02, at 10:19 , Stefan Taxhet (sonews) wrote:
>>>>>>> On 02.02.2011 15:17, Marcus Lange wrote:

Hi Stuart,

>>>>>> Sending to the RC10 seems better,
>>>>> That would not be my favorite choice. As Marcus explained the RCs=20
>>>>> are not approved yet. That's why I thought the other.html might be =

>>>>> better as it gives the choice to pick 3.2.1 or follow the link to=20
>>>>> the RC.
>>>> Why not add just a caveat to the link, "Not fully tested, use at=20
>>>> your own risk. For a proven version, use 3.x.x" (3.2.1, in this case=
).
>>>
>>> there are already hints on webpages (download.openoffice.org, see the=
=20
>>> yellow box and download.openoffice.org/all_rc.html, see the=20
>>> disclaimer text).
>>
>> Evidently=85 it's not enough.
>=20
> Clearly en-GB is not the only build in this state - about half the=20
> release download matrix is still not up-to-date.  It may help to add a =

> note on the release download page stating when the first binary of 3.3 =

> was distributed and the cut-off date for testing RCs so users can get a=
n=20
> idea of a) the newness of this release, and b) the fact we can't get al=
l=20
> possible variants QA'ed at the same time so patience may be needed.

the problem with updating the entry webpage of the download portal is=20
that it is a dynamically generated webpage. So, I didn't want to update=20
it with static text here and then.

Furthermore, I don't think that it will help to prevent the problem when =

see user can see since when the release has gone live and how long the=20
RC testing phase will last.

The real problem is that the user sees (or knows already) that the=20
release is done, then clicks on the green download button but doesn't=20
get a build because his language is not yet tested; or at least not all=20
platforms/builds.

This could be solved a) when all NLC teams can test their builds or b)=20
with implementation of a very detailed error management for the JS magic =

that lies behind the download webpage.

a) cannot be solved because not every team has testers for all available =

platforms
b) is very complex and time consuming to fullfill, currently we have not =

the resources to do so as the successfully migration to Kenai is more=20
important.

I know it's not a good situation but IMHO we have to live with the=20
current situation.

Best regards

Marcus