preferred bugzilla category for test release 3?

[Michael Wiktowy]

Hi,

I was playing around with test3 LiveCD yesterday (excellent job BTW
... I was able to install and use Beryl all within the LiveCD
environment) and submitted a few bugs that I found (not specifically
about Beryl ... I was just pretty happy it and Compiz finally works on
my ATI 800XL out of the box).

When looking through the components and products that you can choose
from I found things a little ambiguous as to the best selections of
categories.

I just picked Fedora Core instead of Extras ... with the merging of
those two, will there still be some sort of line between the for bug
reporting?

Also, there was "devel" and "test3" there ... which is the best place
to put reported bugs under when testing f7test3 so they won't get
overlooked ... all the other test categories were labeled f(x)test(y),
etc. but there was no f7test3? I just picked "devel" since I wasn't
sure if testx categories were just leftovers from a previous release.

/Mike

[Will Woods]

On Fri, 2007-03-30 at 16:07 -0400, Michael Wiktowy wrote:
> When looking through the components and products that you can choose
> from I found things a little ambiguous as to the best selections of
> categories.
>
> I just picked Fedora Core instead of Extras ... with the merging of
> those two, will there still be some sort of line between the for bug
> reporting?

We haven't decided what we're going to to in the Grand Future of the
Unified Fedora. We may just have one Product (Fedora) and two versions
(f7 and devel). When we release f8, we'll make a new 'f8pre' version to
hold all the old 'devel' bugs from f7->f8. And so on.
> Also, there was "devel" and "test3" there ... which is the best place
> to put reported bugs under when testing f7test3 so they won't get
> overlooked ... all the other test categories were labeled f(x)test(y),
> etc. but there was no f7test3? I just picked "devel" since I wasn't
> sure if testx categories were just leftovers from a previous release.

Use 'devel'. We're not creating individual versions for each test
release anymore.

When F7 is finally released we'll probably end up mass-moving the
'devel' bugs to 'f7pre' or something.

-w

[Matthew Miller]

On Fri, Mar 30, 2007 at 05:08:24PM -0400, Will Woods wrote:
> We haven't decided what we're going to to in the Grand Future of the
> Unified Fedora. We may just have one Product (Fedora) and two versions
> (f7 and devel). When we release f8, we'll make a new 'f8pre' version to
> hold all the old 'devel' bugs from f7->f8. And so on.

Rather than creating new "cruft bins" every release, I'd encourage creating
"reported-against-f7devel" keyword (and new ones), and when the release
happens, moving all open devel bugs to NEEDINFO at tagging them with the
appropriate keyword and a notice that the bug needs retesting against the
released product.

[Michael Wiktowy]

Thanks ... that jives with my assumptions about what to do.

That field could probably be boiled down to stable and rawhide

/Mike

[Jesse Keating]

On Friday 30 March 2007 18:11:55 Matthew Miller wrote:
> Rather than creating new "cruft bins" every release, I'd encourage creating
> "reported-against-f7devel" keyword (and new ones), and when the release
> happens, moving all open devel bugs to NEEDINFO at tagging them with the
> appropriate keyword and a notice that the bug needs retesting against the
> released product.

Sure, that could work.  The basic idea is to keep the devel release free of 
the cruft so that searching for bugs is quicker and such.