there is a command in fedora-supybot called pushduty -- the code basically looks at the calendar release-engineering on fedocal and returns stuff.
However, on zodbot, there is an alias for pushduty too, that returns:
.alias pushduty
[STOP RUNNING THIS ADAM JEEZ. YOU AREN'T GOING TO MAKE PUSHDUTY HAPPEN]
and running the Fedora version seems to be limited to bot owners for some reason: .Fedora pushduty
.Fedora pushduty
Error: You don't have the fedora.pushduty capability. If you think that you should have this capability, be sure that you are identified before trying again. The 'whoami' command can tell you if you're identified
isa this an old thing that never took off, and if so can i remove it from supybot-fedora>?
@adamwill Do you know anything about this feature?
Metadata Update from @zlopez: - Issue priority set to: Waiting on External (was: Needs Review)
So this is from the time where compose were done manually. We had a person responsible to kick the compose and push manually every day and we would rotate through the people having the knowledge and access to do this every week. We thus had the ".pushduty" command to know who was responsible for doing it this week conveniently on IRC.
Since then the composes are signed and pushed automatically (thanks robotsignatory!), so this command is no longer used. I figure @adamwill kept on using it every now and then, which resulted in the alias being created to gently remind him that it is no longer needed :)
So imho, this command can be dropped.
Uh, IIRC it wasn't about composes, or wasn't only about composes, but also about stable push requests during freezes. Like right now. Pushing F35 updates stable is a manual operation because we're in the Beta freeze. If I want to get a stable push request handled right away, I need to know who to bug. At some point there was a rota for that, and .pushduty told me who was on that job at a given time. Now I think it's always @mohanboddu or whoever's covering for him if he's away, which might be why the alias got done.
Right, what everyone said.
I think we can drop this. I think for stable pushes it should be: If in EU timezones, ping @humaton If in US timezones, ping @mohanboddu * If either are not available or on pto, ping @kevin
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Waiting on External)
So, lets drop this from fedora plugin and we can use the alias version to adjust it now to whatever we want if we want to provide guidance who is available.
I changed the alias to:
EU: jednorozec, NA: mboddu, otherwise: nirik
for now.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.