Gerrit was updated from 2.13.14 (EOL) to 2.14.20 (also EOL)

After adapting the appropriate configuration changes, everything that 
was working before appears to still work.  If there are any regressions, 
please tell me and/or file a bug ticket.

The big gotcha is that 2.14.x supports a "new UI" -- but due to bugs in 
the 2.14 release series and strict security defaults in modern browsers, 
the "new UI" doesn't actually work due to mixed http/https content. So 
don't try to enable it!  If you accidentally turn it on and get stuck, 
see this page for instructions on how to revert to the old UI:

  https://www.gerritcodereview.com/2.14.html#new-user-interface-polygerrit

(I also have this logged as FS#13210)

The oauth plugin was updated too, which should hopefully silence the 
github nastygram we were getting about relying on an obsolete API.

Speaking of the oauth plugin -- the newer version supports using gitlab 
as a backend, and I tried to enable this only to stumble into a strange 
URI mangling bug which results in authentication attempts failing.  So, 
gitlab integration will remain disabled for now.

Looking forward, I intend to continue upgrades from 2.14.x to 2.15.x, 
and from there to 2.16.x, which is still supported by upstream.  That 
will also pull newer versions of the oauth plugin.

Meanwhile, if anyone has suggestions for quality-of-life plugins or 
other enhancements, please holler.

Cheers,

 - Solomon
-- 
Solomon Peachy                        pizza at shaftnet dot org (email&xmpp)
                                      @pizza:shaftnet dot org   (matrix)
High Springs, FL                      speachy (freenode)

Attachment: signature.asc
Description: PGP signature

Reply via email to