#296: Fix blocker bug tracker page and replace it with a static HTML page
-----------------------+-----------------------
Reporter: adamwill | Owner: tflink
Type: task | Status: new
Priority: major | Milestone: Fedora 18
Component: Wiki | Version:
Resolution: | Keywords:
Blocked By: | Blocking:
-----------------------+-----------------------
Comment (by tflink):
Replying to [comment:4 johannbg]:
> There is nothing wrong with using some other solution but that means a
lot of work moving things from the wiki into that new thing or coming up
with a front end that keeps tap of all this stuff and presents it to
reporters for easy accessing.
>
> If I can recall correctly the only solution suggested at that time that
held any potential water for success for the community, was the Fedora
community app which at that time was in (very) early stages and which
current status I'm unaware of. ( Reporters would just log in and all
relevant information would be presented to them or within a grasp )
>
> We did look at various testing platforms ( not only for this ) but they
as well fell short one way or another...
I wonder if there's been some miscommunication here. We're not proposing
to change the test matrices or anything else on the wiki, just the blocker
tracking page which is generally read-only. All the script would do is
gather all the current release blocking bugs and generate HTML to display
all of them in one place.
While I think that there could be some advantages in investigating a
different test case management system in the future, I agree that it would
require much more than 10 minutes at one QA meeting to come to an
agreement on whether it was a good idea and which system to go with.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/296#comment:5>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
