Dear Sophie,

Dne ponedeljek, 06. avgust 2012 je pošiljatelj Sophie Gautier <
gautier.sop...@gmail.com> napisal:
> Hi Michael, all,
> On 06/08/2012 12:04, Michael Bauer wrote:
>>
>> Hi Sophie,
>>
>> 06/08/2012 10:53, sgrìobh Sophie Gautier:
>>>
>>> How many of your community have tested the RCs of this last version.
>>
>> I'm barely getting enough sleep at the moment so probably no-one - there
>> aren't enough tech-savy users in my community who would know the
>> difference between the release and the RC, let alone use them. We
>> actually run install sessions because most people are unsure about how
>> to install it to begin with (which is, by the way, a general problem,
>> not a specific LO issue).
>>
>> And before you chide me for not trying the RC - I did a lot of testing
>> before our first release and during the first few version following
>> that. I then got lax because I somehow assumed that people wouldn't
>> break something critical that already worked and then release it. I run
>> over two dozen localization projects for my locale, I'm sorry but that
>> means I have to make some concessions to my need for sleep ;)
>
> Most of us here are in the same case of doing our best for the release.
My question is how we can teach the users, bring interest to them to
participate and not only be users at the end of the process.
>>
>>> Rejecting the fault and criticizing others won't help to respect our
>>> release plan which is as important for the companies providing tested
>>> and certified versions of our software as bug free versions.
>>
>> Since when did the release plan become so important that it can't be
>> nudged when needed? It's a plan, not the holy grail.
>
> The release has already been delayed for a week. You know that when this
bug is very important for you, another one will be very important for me,
and still another one for my neighbor, we could delayed it for weeks...

Well, spell checking is a major thing for all users in an office suite.

So we will release 3.7 if printing only works with a workaround, and 3.8.0
if keyboard only works with a workaround?

If LO would not set this release date in the summer vacation period of the
northern hemisphere, maybe more of us would be able to test... so that is
my advice for future release plans.

>>>
>>> Again, I ask that question: what would be your solution to improve the
>>> QA situation in the frame of our development process ?
>>
>> To have a bigger team and I'm working on that but until that happens, I
>> can't do much except to start using the RCs in future rather than the
>> releases because having a larger team will mean having to pay them.
>> Which of course makes providing support tricky, if I'm looking at a
>> different version on screen than the person at the other end of the
>> screen or phone. >.<
>
> what would help to bring more people in ? tools, process, meetings ? how
can we bring our community to help here, not only by meaning you investing
more time (this is not my aim really :) but by having an attractive QA
process ?
>
> Kind regards
> Sophie
>>
>> Michael
>>
>
>
> --
> Sophie Gautier <sophie.gaut...@documentfoundation.org>
> Tel:+33683901545
> Membership & Certification Committee Member - Co-founder
> The Document Foundation
>
> --
> Unsubscribe instructions: E-mail to l10n+h...@global.libreoffice.org
> Problems?
http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
> Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
> List archive: http://listarchives.libreoffice.org/global/l10n/
> All messages sent to this list will be publicly archived and cannot be
deleted
>

-- 
Unsubscribe instructions: E-mail to l10n+h...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted

Reply via email to