Re: Prioritizing different possible optimization work for composes

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

 




2. Making composes self-service, so QA can initiate them with a button
  

On Mon, Oct 2, 2017 at 11:27 PM, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote:
Hey, here's a question: if you had a choice to improve how the compose
process goes leading up to releases (beta or final), as a Fedora QA
person would you prefer:

1. Vastly increased speed of compose so we can do more than one per
   day, or

2. Making composes self-service, so QA can initiate them with a button
   (possibly in the blockerbugs app)?

Which of these would be more helpful? I mean, ideally, we have both,
but which would you rather worked on first?


--
Matthew Miller
<mattdm@xxxxxxxxxxxxxxxxx>
Fedora Project Leader
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@lists.fedoraproject.org



--
Hrushabh Sirsulwar
about.me/hrushabhs
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx

[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux