Fix #22: Don't mark release as critical if it's less than a month old

[lewisgoddard]

• Fixes Don't mark release as critical if it's less than a month old #22: Don't mark release as critical if it's less than a month old
• Get now and release_date as integers.
• Stop marking recent releases with warnings and criticals.
• Warn over 50 commits, even with recent releases.

[cassidyjames]

I was looking at this in smarter-critical-badge, but something I was thinking about was trying to share more meaning behind the why of the status.

[lewisgoddard]

Ah, this was based on work I was doing for my fork and I already have a timeago field there which kind of handles that. https://releases.eustasy.org/

[cassidyjames]

@lewisgoddard yeah by I think there can still be a disconnect between, "well this one has 50 commits and is red, why is this one with 72 commits not?" or whatever the exact numbers are. I guess I want to think about if we can convey statuses in a better way. :) Not-fully-thought-out designing incoming…

Maybe something like:

• Recent Release (green)
• Up to Date (green)
• 2–15 commits (but not recently released) (gray)
• 16–50 commits (but not recently released) (yellow)
• 51+ commits (but not recently released) (red)

And then each might have qualifying data below that for context. I.e.:

Recent Release
2 days ago

[lewisgoddard]

@cassidyjames Want to take another look at this? Haven't styled it, just semantically works like you wanted.

[jeremypw]

@cassidyjames @danrabbit @davidmhewitt There are outstanding review requests but no activity for quite some time. Maybe it should be converted to draft or closed if there is little chance of it getting merged? I do not have rights to do this.