What's the description for it?

CC: (none) => rdalverny

known problems with Mageia and with fix or workaround

something like that

(you were quick)

I'm afraid the use case is not clear enough, or it's too early for me :-)

What will be the use of the keyword then? searching for all known/confirmed bugs that have a fix/workaround (then likely to be resolved:fixed already)?

Status: NEW => ASSIGNED

Don't really know myself :/

but ahmad used this one for add some entry in http://www.mageia.org/wiki/doku.php?id=mageia1:errata

Ok, so I found this discussion that could explain: http://lists.mandriva.com/bugteam/2009-05/msg00022.php : errata keyword would be used by packagers to remember what bug (being still open, or resolved for a later release) to have listed in the release errata.

That's a good idea, but... the errata doc is constantly evolving from alpha1 to final (what was an errata for alpha2 may be fixed, hopefully, for beta1).

So there's still a manual process to check what is to be put in the errata notes (that will be freezed at the final release, so any later change to an errata bug should not affect it).

This still makes sense, but this keyword use case and description really must be clear, understood and managed by release managers and maintainers. Has this been discussed in QA or dev teams?

>Ok, so I found this discussion that could explain:
>http://lists.mandriva.com/bugteam/2009-05/msg00022.php :

Yes I see this thread after my comment 4

>So there's still a manual process to check what is to be put in the errata
>notes (that will be freezed at the final release, so any later change to an
>errata bug should not affect it).

freezed ? you are sure ?
It's not the release note ? If a bug is really resolved we can change it the page.

>This still makes sense, but this keyword use case and description really must
>be clear, understood and managed by release managers and maintainers. Has this
>been discussed in QA or dev teams?

I have only asked on the packager meeting but there was no real discussion.
http://meetbot.mageia.org/mageia-dev/2011/mageia-dev.2011-11-30-20.13.log.html#l-157

(In reply to comment #6)
> >So there's still a manual process to check what is to be put in the errata
> >notes (that will be freezed at the final release, so any later change to an
> >errata bug should not affect it).
> 
> freezed ? you are sure ?
> It's not the release note ? If a bug is really resolved we can change it the
> page.

Yes, but the errata is valid for a fresh install from the released ISO too. That does not exclude later updates to fix an errata issue, the notice must still be there for those that won't have the possibility to install updates at once (or at all).

> I have only asked on the packager meeting but there was no real discussion.
> http://meetbot.mageia.org/mageia-dev/2011/mageia-dev.2011-11-30-20.13.log.html#l-157

Checked ok. Then what's needed is a clear description of when to use this keyword (in Bugzilla, and outside of it).

For the development of Mageia 5, we have used two whiteboard tags for errata bugs: ERRATA (bugs that will affect the released Mageia 5 and are present in the wiki errata) and FOR_ERRATA (same kind of bugs, but not listed in the wiki yet), the idea being that FOR_ERRATA bugs need to be turned to ERRATA at some time.

I don't know if it's sufficient or if keywords would be better suited than whiteboard tags.

IIRC we used FOR_ERRATA and IN_ERRATA for Mageia 5 in order to avoid the confusion on the meaning of ERRATA.

I'm considering switching to FOR_ERRATA{5,6,...} and IN_ERRATA{5,6...} actually, because this could help for triage and writing of Errata pages.

(In reply to Samuel VERSCHELDE from comment #9)
> IIRC we used FOR_ERRATA and IN_ERRATA for Mageia 5 in order to avoid the
> confusion on the meaning of ERRATA.
> 
> I'm considering switching to FOR_ERRATA{5,6,...} and IN_ERRATA{5,6...}
> actually, because this could help for triage and writing of Errata pages.

Which implicitly answers the question about keywords: if we do that, whiteboards will fit better.

The FOR_ERRATA5, FOR_ERRATA6, IN_ERRATA5 and IN_ERRATA6 keywords are already in use, which means this bug is fixed.

Personally, I think a flag would be better than a keyword, because FOR_ERRATA and IN_ERRATA are mutually exclusive, which is exactly what flags are used for.

Resolution: (none) => FIXED
Status: ASSIGNED => RESOLVED