[Maniphest] [Created] T33: Blocker Proposal is Slow
by tflink (Tim Flink)
mkrizek created this task.
mkrizek added a subscriber: mkrizek.
mkrizek added a project: blockerbugs
TASK DESCRIPTION
Moved from trac [[ https://fedorahosted.org/fedora-qa/ticket/356 | https://fedorahosted.org/fedora-qa/ticket/356 ]]:
"Problem
While the blocker proposal functionality does work, the process of actually proposing the blocker is very slow - it appears as if the page has just stalled for a while as the request is being submitted to bugzilla
Outside of being an annoyance, there is a possibility of users refreshing the page during submission, which would trigger a second proposal. This isn't the biggest issue ever but could end up generating extra comments in bugs.
Analysis
It would be better to show users a "bug is proposing" page until the proposal is complete - that way they wouldn't be tempted to refresh the page and if the page is done correctly, it wouldn't matter if the page was refreshed or not.
Enhancement recommendation
I have some ideas on how to go about fixing this but I need to explore the details before figuring out if any of them are even practical or how long the implementation would actually take."
TASK DETAIL
https://phab.qadevel.cloud.fedoraproject.org/T33
To: mkrizek
Cc: qa-devel, mkrizek
10 years, 3 months
2013-01-09 @ 16:00 UTC - Fedora QA Devel Meeting
by Tim Flink
# Fedora QA Devel Meeting
# Date: 2014-01-09
# Time: 16:00 - 18:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting-2 on irc.freenode.net
The email feedback I received from folks was from NA and EMEA timezones
and showed a preference for Thursday over Wednesday, and thus we have a
time!
I don't actually plan on this taking up 2 whole hours but given how long
these conversations can take sometimes, figured that having the extra
time for spillover wouldn't be a bad thing. The target is 1 hour or so.
I've put a proposed agenda below. Let me know if you have topics to add
or just reply to the thread on qa-devel@.
Tim
Proposed Agenda
===============
Current Project Status
* blockerbugs
* testdays
* resultsdb
* taskotron
* support tools
Project Priorities
* What do we have to get done vs. what we want to get done
* What can't we do until fedora.next and/or f21 is more figured out
Taskotron
* Deadlines
* Subprojects
* TODO
* Stuff yet to be figured out
- Notifications
- Querying w/ rules/policy
10 years, 3 months
[Maniphest] [Created] T37: Port AutoQA PUATP Checks
by tflink (Tim Flink)
tflink created this task.
tflink added subscribers: qa-devel, tflink.
tflink added a project: taskotron
TASK DESCRIPTION
In order to use the PUATP checks from AutoQA (rpmlint, rpmguard, depcheck, upgradepath) in taskotron, they need to be ported first. This is the tracking ticket for getting those checks ported to a form usable by taskotron (separate git repos, move common functionality into libtaskotron etc.).
TASK DETAIL
https://phab.qadevel.cloud.fedoraproject.org/T37
To: tflink
Cc: qa-devel, tflink
10 years, 3 months