#37: Apex -------------------------------------+------------------------------------- Reporter: ralph | Owner: Type: New badge | Status: idea | closed Priority: minor | Resolution: Keywords: | pushed Has a description: 1 | Has a name: Artwork status: Approved | 1 (design team members only) | Concept approved (reviewers only): External requirements: fedmsg | 0 for fpl status (wiki page | Badge definition status: scrape?) | None Triaged (triagers only): 1 | Manually awarded: | 0 -------------------------------------+------------------------------------- Changes (by ralph):
* status: reopened => closed * resolution: => pushed
Comment:
Yeah, but for such a rare event, it may not be worth investing the time in automation here. If the automation fails, we won't know for the next N years (when the FPL changes next) and then we'll have to notice and spend time figuring out why it didn't work (did we migrate from puppet to ansible in the meantime? did we migrate from ansible to saltstack?)
Having a badges admin manually award the badge to the next FPL once every so many years seems like less work in the long run.