Description: You committed to an EOL release repository. Also, BRAAAAAAAAAINS.
See also, obviously, #72 . After seeing that one I thought some kind of undead/zombie spin would be good, and following the logic of #72, it'd have to be for (trying to) build something older than EOL. Nirik pointed out that 'commit to an EOL git repo' would be a pretty easy condition to use.
Artwork concept: a zombie badger punching out of its grave - I just wanted the classic horror movie shot from ground level with just the 'fist' visible, but I defer to the designers' wisdom :)
The git.receive message should contain all the necessary information (msg.commit.branch), but I'm not sure how we should implement the 'is EOL?' logic.
partial description (missing criteria)
ooh, there can be a headstone with a badger face on it behind the fist - I think decause already had something like that as an alternative design for Old Yeller.
Worth noting that the 'cold undead hands' thing sounds cool, but in practice the metaphor doesn't work (the package is undead, not the badger). if we think people will stop and think about that, it could just be called Back From The Dead or something like that.
Set triaged to 'yes' for all tickets, as I've hit them all already.
just put types back in, we'll try and handle bugs here too, no new trac.
You could copy my approach from the #72 badge and just hardcode the '17' in there. There is a wiki page out there with a list of stuff that needs to be done for each new release cycle on the infra side. We can add updating these two badges to it.
to comment on this ticket.
Copyright © 2014-2017 Red Hat
3.10.1 — Documentation