Hello all,
For a long time now updates are pushed manually everyday. It was troublesome and someone has to own it for a week and look after it.
Now, the pushes are automated and are pushed everyday at 00:00 UTC. If anything fails there will be an oncall person (same person who used to do the pushes) who will take care of the failure.
During release freezes these automated pushes are disabled and are manually pushed by RelEng/Infra. Since freezes should be handled differently this will give RelEng more control over the pushes.
Please let us know if you have any questions or contact us on #fedora-releng on Freenode.
Thanks, Mohan Boddu.
_______________________________________________ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapro...
On 11/7/18 10:44 AM, Mohan Boddu wrote:
For a long time now updates are pushed manually everyday. It was troublesome and someone has to own it for a week and look after it.
Now, the pushes are automated and are pushed everyday at 00:00 UTC. If anything fails there will be an oncall person (same person who used to do the pushes) who will take care of the failure.
During release freezes these automated pushes are disabled and are manually pushed by RelEng/Infra. Since freezes should be handled differently this will give RelEng more control over the pushes.
Please let us know if you have any questions or contact us on #fedora-releng on Freenode.
While many may not see this as significant I see this as a giant leap forward. Great job everyone!
On 11/7/18 1:35 PM, Michael Cronenworth wrote:
On 11/7/18 10:44 AM, Mohan Boddu wrote:
For a long time now updates are pushed manually everyday. It was troublesome and someone has to own it for a week and look after it.
Now, the pushes are automated and are pushed everyday at 00:00 UTC. If anything fails there will be an oncall person (same person who used to do the pushes) who will take care of the failure.
During release freezes these automated pushes are disabled and are manually pushed by RelEng/Infra. Since freezes should be handled differently this will give RelEng more control over the pushes.
Please let us know if you have any questions or contact us on #fedora-releng on Freenode.
While many may not see this as significant I see this as a giant leap forward. Great job everyone!
+1 - great news!
On 11/7/18 1:29 PM, Dusty Mabe wrote:
On 11/7/18 1:35 PM, Michael Cronenworth wrote:
On 11/7/18 10:44 AM, Mohan Boddu wrote:
For a long time now updates are pushed manually everyday. It was troublesome and someone has to own it for a week and look after it.
Now, the pushes are automated and are pushed everyday at 00:00 UTC. If anything fails there will be an oncall person (same person who used to do the pushes) who will take care of the failure.
During release freezes these automated pushes are disabled and are manually pushed by RelEng/Infra. Since freezes should be handled differently this will give RelEng more control over the pushes.
Please let us know if you have any questions or contact us on #fedora-releng on Freenode.
While many may not see this as significant I see this as a giant leap forward. Great job everyone!
+1 - great news!
I'll echo that sentiment. Thanks to everyone who did the work to make this happen!
On 2018-11-07 10:35 a.m., Michael Cronenworth wrote:
On 11/7/18 10:44 AM, Mohan Boddu wrote: >> For a long time now updates are pushed manually everyday. It was
troublesome and someone has to own it for a week and look after it. >>
Now, the pushes are automated and are pushed everyday at 00:00 UTC.
If anything fails there will be an oncall person (same person who used to do the pushes) who will take care of the failure. >> >> During release freezes these automated pushes are disabled and are manually pushed by RelEng/Infra. Since freezes should be handled differently this will give RelEng more control over the pushes. >> >> Please let us know if you have any questions or contact us on #fedora-releng on Freenode. >
While many may not see this as significant I see this as a giant leap
forward. Great job everyone! > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-leave@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Much needed as it is very easy to forget pushing a 14 days testing stage package.
Luya
On Thu, Nov 8, 2018, 00:16 Luya Tshimbalanga <luya@fedoraproject.org wrote:
On 2018-11-07 10:35 a.m., Michael Cronenworth wrote:
On 11/7/18 10:44 AM, Mohan Boddu wrote: >> For a long time now updates
are pushed manually everyday. It was troublesome and someone has to own it for a week and look after it. >> >> Now, the pushes are automated and are pushed everyday at 00:00 UTC. If anything fails there will be an oncall person (same person who used to do the pushes) who will take care of the failure. >> >> During release freezes these automated pushes are disabled and are manually pushed by RelEng/Infra. Since freezes should be handled differently this will give RelEng more control over the pushes. >> >> Please let us know if you have any questions or contact us on #fedora-releng on Freenode. > > While many may not see this as significant I see this as a giant leap forward. Great job everyone! > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-leave@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Much needed as it is very easy to forget pushing a 14 days testing stage package.
Luya
If I understand this announcement correctly, you'll still have to submit requests for getting your packages pushed to stable yourself. This is about making the initiation of the actual masher process automatic instead of manual. (Please correct me if I'm wrong.)
Fabio
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
On 11/7/18 4:27 PM, Fabio Valentini wrote:
If I understand this announcement correctly, you'll still have to submit requests for getting your packages pushed to stable yourself. This is about making the initiation of the actual masher process automatic instead of manual. (Please correct me if I'm wrong.)
Yes, thats right.
In the past the updates pushes were started manually by different releng folks at different times. Now it will start at 00:00UTC everyday. This should allow folks more ability to know when they need to submit things by to get them pushed out that day.
kevin
On Wed, Nov 07, 2018 at 05:15:57PM -0800, Kevin Fenzi wrote:
On 11/7/18 4:27 PM, Fabio Valentini wrote:
If I understand this announcement correctly, you'll still have to submit requests for getting your packages pushed to stable yourself.
What about this part? There's an "Autopush — enabled" item in bodhi, but afaict, it doesn't do anything and I always click "push to batched" manually on all updates. I'd like to have the update got to batched automatically once the 7 days of waiting are up.
Zbyszek
This is about making the initiation of the actual masher process automatic instead of manual. (Please correct me if I'm wrong.)
Yes, thats right.
In the past the updates pushes were started manually by different releng folks at different times. Now it will start at 00:00UTC everyday. This should allow folks more ability to know when they need to submit things by to get them pushed out that day.
Il 11/8/18 8:00 AM, Zbigniew Jędrzejewski-Szmek ha scritto:
What about this part? There's an "Autopush — enabled" item in bodhi, but afaict, it doesn't do anything and I always click "push to batched" manually on all updates. I'd like to have the update got to batched automatically once the 7 days of waiting are up.
Zbyszek
The 'Autopush' happens when the update reaches the karma threshold. It is not applied based on days in testing.
Mattia
On Thu, Nov 08, 2018 at 07:25:10AM +0000, Mattia Verga wrote:
Il 11/8/18 8:00 AM, Zbigniew Jędrzejewski-Szmek ha scritto:
What about this part? There's an "Autopush — enabled" item in bodhi, but afaict, it doesn't do anything and I always click "push to batched" manually on all updates. I'd like to have the update got to batched automatically once the 7 days of waiting are up.
Zbyszek
The 'Autopush' happens when the update reaches the karma threshold. It is not applied based on days in testing.
That's what I thought. This seems bad to me, because it is yet another thing that I need to poke by hand. What I want is that after the update is filed, I never have to think about it again unless somebody provides negative feedback.
Zbyszek
Il 11/8/18 9:07 AM, Zbigniew Jędrzejewski-Szmek ha scritto:
On Thu, Nov 08, 2018 at 07:25:10AM +0000, Mattia Verga wrote:
That's what I thought. This seems bad to me, because it is yet another thing that I need to poke by hand. What I want is that after the update is filed, I never have to think about it again unless somebody provides negative feedback.
Zbyszek
It seems there's already a request for enhancement filled in:
https://github.com/fedora-infra/bodhi/issues/1803
I'll try to work it out.
Mattia
On Thu, 2018-11-08 at 08:07 +0000, Zbigniew Jędrzejewski-Szmek wrote:
The 'Autopush' happens when the update reaches the karma threshold. It
is not applied based on days in testing.
That's what I thought. This seems bad to me, because it is yet another thing that I need to poke by hand. What I want is that after the update is filed, I never have to think about it again unless somebody provides negative feedback.
FWIW, I am beginning to work on a proposal for a new updates policy and I plan for this to be part of it - the update will by default go stable unless a human stops it.
On Thu, Nov 8, 2018 at 3:42 PM Randy Barlow bowlofeggs@fedoraproject.org wrote:
On Thu, 2018-11-08 at 08:07 +0000, Zbigniew Jędrzejewski-Szmek wrote:
The 'Autopush' happens when the update reaches the karma threshold. It
is not applied based on days in testing.
That's what I thought. This seems bad to me, because it is yet another thing that I need to poke by hand. What I want is that after the update is filed, I never have to think about it again unless somebody provides negative feedback.
FWIW, I am beginning to work on a proposal for a new updates policy and I plan for this to be part of it - the update will by default go stable unless a human stops it.
With my QA hat on, I have reservations towards this. It depends on the implementation. Please either send the proposal to devel list, or let the QA team know so that we can provide our feedback. Thanks.
On Fri, 2018-11-09 at 16:25 +0100, Kamil Paral wrote:
With my QA hat on, I have reservations towards this. It depends on the implementation. Please either send the proposal to devel list, or let the QA team know so that we can provide our feedback. Thanks.
Will do - I'm still in the early stages of interviewing stakeholders and getting early feedback, so I haven't written anything cohesive yet. I'd be happy to chat with you 1x1 if you would like.
On Thu, 2018-11-08 at 09:41 -0500, Randy Barlow wrote:
FWIW, I am beginning to work on a proposal for a new updates policy and I plan for this to be part of it - the update will by default go stable unless a human stops it.
I have filed a FESCo ticket to request this change to the updates policy:
On Wed, Nov 07, 2018 at 05:15:57PM -0800, Kevin Fenzi wrote:
What about this part? There's an "Autopush — enabled" item in bodhi, but afaict, it doesn't do anything and I always click "push to batched" manually on all updates. I'd like to have the update got to batched automatically once the 7 days of waiting are up.
Zbyszek
Hi, what about "push to batched": How is this currently handled? Current docs say: "... waiting until the next Tuesday when Bodhi will automatically switch the request to "stable" at 03:00 UTC." [1] Is this still only on the next Tuesday? During the last package updates, which I pushed to batched, it turned out that it was the always next day at 03:00 UTC.
Best regards Wolfgang
On Fri, Nov 9, 2018 at 6:00 AM Wolfgang Stoeggl c72578@yahoo.de wrote:
what about "push to batched": How is this currently handled? Current docs say: "... waiting until the next Tuesday when Bodhi will automatically switch the request to "stable" at 03:00 UTC." [1] Is this still only on the next Tuesday? During the last package updates, which I pushed to batched, it turned out that it was the always next day at 03:00 UTC.
"Push to batched" is currently soft-disabled. (It was too much work at the time we disabled it to actually remove it from Bodhi). FESCo determined that the way it was implemented and the policy around it was not meaningful, so right now "push to batched" just means that an automated script automatically marks it for stable just before the stable push automated run.
The short version of that discussion was that because we still allowed people to push directly to stable if they felt it was early enough, certain packagers who had ideological differences with the batched plan were just ignoring it and always pushing it stable immediately, thereby eliminating the stated benefit of not updating repodata and mirroring every day. We had two choices: make "batched" mandatory for all updates or disabled the batching. FESCo elected to take the latter approach at the time.
On 11/09/2018 02:05 PM, Stephen Gallagher wrote:
On Fri, Nov 9, 2018 at 6:00 AM Wolfgang Stoeggl c72578@yahoo.de wrote:
what about "push to batched": How is this currently handled? Current docs say: "... waiting until the next Tuesday when Bodhi will automatically switch the request to "stable" at 03:00 UTC." [1] Is this still only on the next Tuesday? During the last package updates, which I pushed to batched, it turned out that it was the always next day at 03:00 UTC.
"Push to batched" is currently soft-disabled. (It was too much work at the time we disabled it to actually remove it from Bodhi). FESCo determined that the way it was implemented and the policy around it was not meaningful, so right now "push to batched" just means that an automated script automatically marks it for stable just before the stable push automated run.
I filed https://pagure.io/releng/issue/7915 to move the request to stable cron job from 03:00 to just before the automatic updates push.
On Wed, Nov 07, 2018 at 11:44:29AM -0500, Mohan Boddu wrote:
Now, the pushes are automated and are pushed everyday at 00:00 UTC. If anything fails there will be an oncall person (same person who used to do the pushes) who will take care of the failure.
Amazing! Congratulations!
-
Dusty Mabe -
Fabio Valentini -
Kalev Lember -
Kamil Paral -
Kevin Fenzi -
Laura Abbott -
Luya Tshimbalanga -
Matthew Miller -
Mattia Verga -
Michael Cronenworth -
Mohan Boddu -
Randy Barlow -
Stephen Gallagher -
Wolfgang Stoeggl -
Zbigniew Jędrzejewski-Szmek