Blocker process: tracker bug / whiteboard naming proposal
awilliam at redhat.com
Sun Jan 20 19:27:30 UTC 2013
On Sun, 2013-01-20 at 19:05 +0000, "Jóhann B. Guðmundsson" wrote:
> On 01/20/2013 06:49 PM, Adam Williamson wrote:
> > This is an issue that's come up repeatedly in the past and was also came
> > up during the talk Tim gave on the blocker process on Friday: the
> > feedback from everyone at the meeting (QA people and non-QA people) was
> > that the current names were really bad and confusing. So we're
> > definitely addressing a need here.
> Confusing for whom ( I dont think these are relevant to anyone else then
> those of us that attend the blocker bug meetings )
They absolutely are, because they're what you use to propose blocker
bugs. That affects anyone who is testing or developing Fedora. They also
affect all developers, because they're the ones getting the bug reports:
they need to know what these statuses are and be able to deal with them.
> and can you point me
> to any talk where this has come up?
There've been multiple threads and meeting discussions, I don't have
references handy, but I thought you'd remember that too...
> Freezebreak really? Nice to have is much easier to understand for non
> English speakers.
Well, it's three words that you probably know the meaning of, but what
they really mean in the Fedora process is not at all obvious: in fact if
you just read the words and try to figure out what they mean, you are
very likely to get the wrong result, which is one of the problems we're
trying to solve. If you see a bug that is proposed as 'nice to have' and
then 'rejected', what it sounds like is that someone doesn't want to fix
the bug. The words don't explain, at all, that what's being discussed is
a freeze break exception. The string 'freezebreak' does.
The word is more 'jargon' - it's not really about native English speaker
vs. non-native, but whether you're aware that the word 'freeze' has a
certain meaning in software development. We thought about that, but the
thing is, you kind of _have_ to know that in order to accurately propose
or discuss or understand this type of bug. If you don't know what a
freeze is, then you kind of can't possibly understand the point of the
process. So we thought the word was appropriate to use here. If you
don't know what freezebreak means, you can go and ask about it or Google
it, and the result you get is very likely to explain to you what's going
on: this is not the case for the words 'nice to have'.
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
More information about the test