Delay in pushing to update-testing with critical security updates

[Jon Ciesla]

On Fri, Mar 30, 2012 at 10:55 AM, Kevin Fenzi <kevin at scrye.com> wrote:
> On Fri, 30 Mar 2012 12:15:12 +0200
> Jan Horak <jhorak at redhat.com> wrote:
>
>> Why it takes 12-20 hours to submit critical security update to
>> updates-testing repository? Do we have such long queue or is the push
>> done regularly in long period?
>
> f15/f16 updates pushes take a long time. ;(
>
> There's some things on the horizon that will hopefully make it better:
>
> * Currently updates mashes are done on the rhel6 rel-eng machines.
> When/if we can do them in a mock chroot, they should use the much
> faster Fedora createrepo.
>
> * Currently 1 fedora push can happen at a time. If we can split that
>  out we can push f15 and f16 in parallel and cut way down on time.
>
>> I think we should prioritize 0day security updates a little more if
>> possible. We're struggling with getting enough positive feedback and
>> this is another 12-20 hours delay and we can't start the build nor
>> make and update the day before Mozilla officially releases it.
>
> If you have a specific update thats critical to push out sooner, ask
> rel-eng? (in ticket or #fedora-releng on irc).

Slightly OT, will it be much longer before the next f17 push, or are
we waiting on Beta?

-J

> kevin
>
> --
> devel mailing list
> devel at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel



-- 
in your fear, seek only peace
in your fear, seek only love

-d. bowie