Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


Bonsoir,

Il y a quelques semaines, je vous faisais part d'un problème de disparitions aléatoires d'images sous Impress. J'ai d’abord pensé à mes deux mains gauches, mais visiblement je ne suis pas le seul à rencontrer ce problème, en témoigne les retours sur la liste fr-user ou l’activé sur ce bug : https://bugs.freedesktop.org/show_bug.cgi?id=46447

Il y a perte de données, le bug est confirmé par plusieurs utilisateurs sous différents OS. Il n'y a pas de contournement clairement identifié.

Ceux qui remontent ce bug ne sont que la minorité qui prend le temps de rédiger un rapport de bug, ou de commenter l’existant. Que fait la majorité des utilisateurs touchés ?

Selon tous les critères de LO. Ce bug est un bloqueur


Any software has bugs. All bugs can't be fixed otherwise the product would never get released. Bugs that could block the release must have one of the following *symptoms*:

  * app can not be installed
  * app does not start
  * data loss

C'est bien ce que l'on a

  * crash
  * freeze
  * security bug
  * license problem
  * unusable function

Also some normal bugs might have the above symptoms. The real blockers must fulfill also the following *conditions*:

  * problem must be *reproducible* by more users;

C'est bon

  * if it is not reproducible, it is most likely a problem on the user
    side; also developers need more information from the reporter; it
    is not fair to block the release and all users if the reporter
    does not provide the needed information on time
  * /broken functionality/ must be *regression* against the last
    released version; if it was not reported early, it is a rarely
    used function and the fix could wait until the next release;

là aussi c'est bon, on ne perdait pas ses images régulièrement avant

  * /data loss/ in import/export filters must be /regression/ against
    released versions; LibO has very good import/export filters
    from/into many file formats; they are improved in every release
    but they are never 100%; sometimes they even depend on a missing
    functionality; if the problem is not a regression, it is
    considered as a feature and thus it is not a blocker
  * problem must *affect most users* or there must *not* be a
    reasonable *workaround*; it is bad to block the release and all
    users because of a corner case when a reasonable workaround exists

Il n'y a pas de contournement.

Ce ses propres critères donc, plus aucune version de LO ne devrait sortir tant que ce bug n'est pas résolu.

Y a-t-il seulement un débat sur ce sujet ?

Pierre

--
Envoyez un mail à qa+unsubscribe@fr.libreoffice.org pour savoir comment vous désinscrire
Les archives de la liste sont disponibles à http://listarchives.libreoffice.org/fr/qa/
Tous les messages envoyés sur cette liste seront archivés publiquement et ne pourront pas être 
supprimés

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.