Adam Williamson wrote:
> But the key principle here isn't 'fairness', it's 'is the package
> broken'. That's the actual thing we're trying to achieve. From that
> perspective it doesn't make any sense to start the timer on submission
> rather than push.
What I want to achieve is predictability
On Tue, 2019-08-13 at 23:36 +0200, Kevin Kofler wrote:
> Adam Williamson wrote:
> > It's not really about "accountability", it's simply: we can only really
> > assume the package is being tested once it makes it to the repo. Yes
> > you can pull it out sooner manually or using bodhi CLI, but very
Adam Williamson wrote:
> It's not really about "accountability", it's simply: we can only really
> assume the package is being tested once it makes it to the repo. Yes
> you can pull it out sooner manually or using bodhi CLI, but very few
> people do that. The intent of the rule is "we want people
On Sun, 2019-08-11 at 12:55 +0200, Kevin Kofler wrote:
> Kevin Fenzi wrote:
> > I'm not sure what else you would like me to do here...
>
> How about changing the Bodhi rules to allow stable pushes 7 days after
> update submission rather than 7 days after the push to testing actually
> happens?
On 8/11/19 3:55 AM, Kevin Kofler wrote:
> Kevin Fenzi wrote:
>> I'm not sure what else you would like me to do here...
>
> How about changing the Bodhi rules to allow stable pushes 7 days after
> update submission rather than 7 days after the push to testing actually
> happens? That would make
Brian (bex) Exelbierd wrote:
> I didn't see your comment until after I opened
> https://pagure.io/fesco/issue/2207 - would love your feedback on that.
https://pagure.io/fesco/issue/2207#comment-589009
Kevin Kofler
___
devel mailing list --
Kevin,
I didn't see your comment until after I opened
https://pagure.io/fesco/issue/2207 - would love your feedback on that.
regards,
bex
On Sun, Aug 11, 2019 at 1:01 PM Kevin Kofler wrote:
>
> Kevin Fenzi wrote:
> > I'm not sure what else you would like me to do here...
>
> How about
Kevin Fenzi wrote:
> I'm not sure what else you would like me to do here...
How about changing the Bodhi rules to allow stable pushes 7 days after
update submission rather than 7 days after the push to testing actually
happens? That would make things much more predictable for maintainers and
> But there's not anything actually wrong anymore?\
>I'm not sure what else you would like me to do here...>kevin
Yeah it's all good now -- f30 and f29 are all in testing now. Thanks for
checking.Phil___
devel mailing list --
On 8/10/19 5:34 PM, Philip Kovacs via devel wrote:
> UTC 00:00:00 has come and gone and nothing was pushed to testing, yet again.
Updates pushes are not instant. You shouldn't expect them all to finish
at 00:00:01. They did indeed fire off as expected at 00:00 and finished
some hours later, as
UTC 00:00:00 has come and gone and nothing was pushed to testing, yet again.
My reference to "7 days" was the time I have to wait until I can request
stable.That timer cannot start until the packages hit testing.
There really should be more than one guy who happens to be at a
conferencetaking
On 8/10/19 11:33 AM, Philip Kovacs via devel wrote:
> Just look at the updates pending pages. Here are f30 and f29, resp:
> https://bodhi.fedoraproject.org/updates/?releases=F30=pending
> https://bodhi.fedoraproject.org/updates/?releases=F29=pending
Updates are pushed every single day at
Just look at the updates pending pages. Here are f30 and f29, resp:
https://bodhi.fedoraproject.org/updates/?releases=F30=pending
https://bodhi.fedoraproject.org/updates/?releases=F29=pending
On Saturday, August 10, 2019, 02:29:24 PM EDT, Stephen John Smoogen
wrote:
On Sat, 10 Aug
On Sat, 10 Aug 2019 at 13:22, Philip Kovacs via devel <
devel@lists.fedoraproject.org> wrote:
> Why does it take days sometimes just to start the 7 day timer?
>
Can we have some examples to track this down? Because without that.. no
idea and no way to fix.
>
Why does it take days sometimes just to start the 7 day timer? ___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
15 matches
Mail list logo
