Is your feature request related to a problem? Please describe.

I made the following ask in the Python Release Managers mailing list and @ewdurbin suggested I file a ticket here. Cut-n-paste:

What do you think about adding the latest point release to the “Active Python Releases” table on the downloads page? This table holds a lot of great information except for the latest point release in each series.

I ask for a selfish reason. I try to keep the CI images up-to-date, but I rely on python-committers emails from all of you to know when to trigger (manual) updates to my dockerfile and readme. Interestingly enough, Larry’s announcement of 3.5.10 made me want to look and be sure I was up-to-date on all releases.

Guess what? I wasn’t! I was 3 releases behind on 3.5 and one behind on 2.7. I think I’m up-to-date on the others (pending my next commit+push). It turns out to be kind of a PITA to find out what the latest point release is for each series.

The “Looking for a specific release?” section isn’t so helpful because there are so many interspersed releases, and I really can't click through a bunch of links to find this information.

So I’m thinking, IWBNI the latest point releases for each active release were captured in one place, and the “Active Python Releases” table seems like the perfect place for that.

Describe the solution you'd like

Add a column to the table, fed by the database (as suggested by @benjaminp), perhaps called "Latest release" which would include the most recent point release (e.g. 3.8.5).

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context

Benjamin followed up:

There's a is_latest flag on the database model for releases [1], so I assume it would just be a matter of plumbing.

[1]