Now you see why I and some others asked you to wait for more testing: https://bugzilla.redhat.com/show_bug.cgi?id=1415137 So pushing on monday was really the wrong solution. Such things *have* to be handled more carefully! On 01/21/2017 04:15 PM, Kai Engert wrote: > On Sat, 2017-01-21 at 15:47 +0100, Christian Dersch wrote: >> On 01/21/2017 03:44 PM, Christian Dersch wrote: >>> Autokarma just means the package will not be pushed automatically, but >>> karma mechanism is still active. So once your update reached the >>> stable karma level you defined, you can hit the push to stable button. >>> If level is not reached you have to wait 7 days (but thats the case >>> with autokarma too), but as the update contains prominent applications >>> I don't expect it takes so long ;) >> Just forgot: Until monday is a *short* time, we have weekend and the >> update did not reach testing yet. I suggest more time. > I've disabled autokarma. > > The current Firefox 50.x will go unsupported on Tuesday, replaced by Firefox 51. > Usually new important security fixes are contained in the new Firefox update. > > Unless we want to delay Firefox 51, this update must go out earlier, or at the > same as Firefox 51. > > I suggest that we make a broad call for getting this update tested widely by > Monday. > > Kai > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
