Release Criteria

[George Staikos]

On November 14, 2002 14:46, Roberto Selbach Teixeira wrote:

> > I'm sure that there will be some documentation and i18n feedback too.  I
> > don't know enough about those processes to insult the team members with
> > an attempt at determining what makes their work "ready to ship".
>
> Since I share my life with the Brazilian translation team coordinator, I
> think I can say something about the subject and risk sleeping in the couch
> ;)
>
> Translations are even more important than most realise. Often I find small
> translation problems in KDE, but sometimes there are some really nasty
> ones. For the end user, a bad translation can ruin a great interface. The
> most common problem is literal translations. This is something we should
> all be very alert about. Most of us don't even read the text anymore and
> thus we tend to let those bugs escape. The checklist should be used to
> verify that at least in the most visible areas the translations are ok.

  Do you think it is feasible to get an "Ok" from the coordinator for each 
translation team before?  That would distribute things evenly and should be 
fairly efficient.  If a team doesn't give an "Ok", then that means their 
translations should not be shipped imho.  This won't work for 3.1 since the 
deadline is too soon, but would it work for future releases?  Is this close 
to what you do already?

> Also, there should be a minimum percentage of messages translated to some
> language for it to be released with KDE. Mixing untranslated strings with
> translated ones looks quite unprofessional. I think this is already done by
> Thomas Diel but this should be in the checklist nonetheless.

   Yes that seems reasonable to me.

-- 

George Staikos