This adds some more details to features that are available in PostgreSQL 12
on the about page, including updated statistics. Additionally, updates the
press FAQ with information around PostgreSQL 12 (and PostgreSQL 13).
Updated the press kit page for the content related to PostgreSQL 12.
This includes translations of the press release into the following
languages with credits to the people who helped:
- Chinese (Daojing Zhou)
- French (Stéphane A. Schildknect, Jean-Christophe Arnu)
- German (Andreas 'ads' Scherbaum, Andreas Kretschmer)
- Hebrew (Michael Goldberg)
- Japanese (Haruka Takatsuka)
- Portuguese (Euler Taveira)
- Russian (Nikolay Samokhvalov)
- Spanish (Mariano Reingart)
In other words, this took one additional step when we put it on production,
but developer environments will now be spared, and we should know better
for adding this for v13 and beyond.
Most providers today are OAuth2, but not all. Much is the same, but some
parts of the flow are fundamentally completely different. So we need a
separate implementation for it.
Previously we let oauthlib handle it and it turned it into an exception
aborging the login. Instread of that, turn off the handling in oauthlib
and manually verify the scope, logging a warning.
Prompted by the fact that Google suddenly started changing the scope of
logins by adding openid connect information even when not asked for.
The fact that we tried to populate it already in the definition of the
form broke the ability to run "migrate" on a completely new system.
Issue reported by Andrew Dunstan
The donations link for PgEU can in fact not be used to donate funds
earmarked for any particular usergroup or activity, so remove the
wording which implied that.
This also fixes a missing </p> tag in an adjacent part of the page,
no visible changes expected since browsers are very good at injecting
these themselves.
Reviewed-by: Magnus Hagander
Discussion: http://postgr.es/m/30D2592C-B495-42A7-B908-33C36793E773@yesql.se
The old message included the exception text in the log message, without
actually assigning the exception. Since it is only called on timeout,
instead just spell out that it's a timeout.
Instead of splitting them up in community events and non community
events, list them all in one block (still indicating badged events using
the badge icon). This makes it more similar to the frontpage, and avoids
"punishing" non-community events by pushing them to to far below the
fold.
The yum project has switched to single-reporpm-for-multiple-versions as
well as putting them in a dedicated directory. This makes a lot of the
cruft in the code to deal with the distribution of reporpms unnecessary,
so change it.
We still need to keep track of which platforms exist for which versions,
so we do still need some spidering, but it's alot simpler.
Since all versions are also always availeble, the javascript that
populates the version list can now just use the list of supported
versions. This could be rendered directly in the HTML, but we might need
to restrict versions-per-platform at some point in the future, and
javascript is needed anyway for the rest of the page, so we keep doing
it the old way.
