[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Urgent bug triaging task: installer blocker bugs for the beta

What to do in this cases:

1 - The bugs status should be preserved as NEW, because I changed a bug to ASS and devel back to NEW ( 490660 )

2 - Some bugs already have other blocks alias like FedoraServerTracker, AnacondaStorage ( 487669, 484983 )

3 - Some bugs already have F11Blocker or F11Beta, but status is NEW, keep it? ( 490515 )

Thanks for clarifications.

I'm afraid making mistakes.


- -
iarly selbir | ski0s


On Wed, Mar 18, 2009 at 4:46 PM, Adam Williamson <awilliam redhat com> wrote:
Hi, guys. If anyone can help with that, it'd be really useful. The
release engineering team needs a decent idea of what really serious bugs
have been filed on the installer since the Alpha release. This is the
list of untriaged bugs:


if anyone can help go through that list and triage the bugs - especially
putting really serious issues that should block the beta release on the
blocker list, i.e. set them to block 'f11beta' - that'd be really great.
Serious issues that maybe shouldn't block the beta but should block
final release should be set to block 'f11blocker' or 'f11target'.

Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org

fedora-test-list mailing list
fedora-test-list redhat com
To unsubscribe:

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]