Proposal: Target tracker bugs

[James Laska]

On Wed, 2010-03-24 at 16:46 -0400, Bill Nottingham wrote:
> James Laska (jlaska at redhat.com) said: 
> > I'm wondering if we need a method for critpath packagers/developers to
> > get non Blocker fixes in.  The case I'm seeing now is that there are
> > bugs against critpath components that are not blocking release criteria
> > (aka not on Blocker list) but are still 'nice to have' low-impact +
> > tested fixes.  These seem sensible to include.  It's not clear how to
> > get those fixes into the release?  So because they're not on the Blocker
> > list, they're just going into F14.
> 
> Are you actually seeing evidence that they're going into F14, rather
> than people just building them for F13 and pushing updates through
> bodhi?

Yes, the data is limited to the install path stuff given that's one
place we've invested in for TC1 [1].  Only Blocker bugs (F13Blocker and
F13Beta) are being pulled in.  Which isn't generally a bad thing, these
are bugs that affect the established release criteria.  But for issues
that don't explicitly affect the criteria (aka 'nice to have') ...
they're going into f14.  

Thanks,
James

[1]
https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : http://lists.fedoraproject.org/pipermail/test/attachments/20100324/2006307e/attachment.bin