Re: Pondering security update time frames

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

 



On Tue, Oct 25, 2016 at 07:37:32PM -0600, Kevin Fenzi wrote:
> Nope. We have talked about having some kind of fast track, but IMHO, we
> should just get the normal process faster. 

Getting the normal process faster would help in a large number of other
areas. Right now, when we have issues in a spin or other deliverable,
we have to first update the RPM, wait for it to get pushed to testing,
wait for it to get pushed to stable, and then wait for a new release
artifact (iso, qcow, whatever) with that RPM included. This means it
can take several days from fix to testing the fix, and if it takes
several tries to get right, it can easily take a week to address a
simpel problem. It'd be nice if we could reduce that turn-around time
to hours, if not minutes.



-- 
Matthew Miller
<mattdm@xxxxxxxxxxxxxxxxx>
Fedora Project Leader
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux