Last modified: 2014-11-06 10:09:48 UTC
Released yesterday, contains several fixes some of us are interested in, e.g. for the new change screen (http://etherpad.wikimedia.org/p/new-gerrit-change-view-comments ); in particular https://code.google.com/p/gerrit/issues/detail?id=2456 . The full list of issues fixed since 2.8.1 should be <https://code.google.com/p/gerrit/issues/list?can=1&q=label%3AFixedIn-2.8.4+OR+label%3AFixedIn-2.8.3+OR+label%3AFixedIn-2.8.2&colspec=ID+Type+Stars+Milestone+Status+Priority+Owner+Summary&cells=tiles>
Just got a series of good news: Updates: Status: Released Affected issues: issue 348: Comment on a patchset should be linkable/bookmarkable http://code.google.com/p/gerrit/issues/detail?id=348 issue 2527: [New change screen] No links to gitblit anywhere http://code.google.com/p/gerrit/issues/detail?id=2527 issue 2528: [New change screen] Confusing how to publish inline comments http://code.google.com/p/gerrit/issues/detail?id=2528 issue 2530: [New change screen] No way to diff ignoring whitespace changes http://code.google.com/p/gerrit/issues/detail?id=2530 issue 93: Display inline file comments below change message in ChangeScreen http://code.google.com/p/gerrit/issues/detail?id=93 https://code.google.com/p/gerrit/issues/list?can=1&q=label%3AFixedIn-2.8.4+OR+label%3AFixedIn-2.8.3+OR+label%3AFixedIn-2.8.2+OR+label%3AFixedIn-2.8.5&colspec=ID+Type+Stars+Milestone+Status+Priority+Owner+Summary&cells=tiles https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.8.5.html 2.9: https://code.google.com/p/gerrit/issues/list?can=1&q=label%3AFixedIn-2.9 https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.9.html
Upgrade to gerrit 2.9 got WONTFIXed at bug 68271. So, I doubt that 2.9 will happen soon for us. gerrit 2.8.x would be easier, but if we upgrade, we should rather use >= 2.8.6 since it had the SSHD issue (bug 53895) fixed that we'd otherwise have to patch in. But as 2.8.6 is broken, 2.8.6.1 would be the only viable option. But as it seems that wmf's investment in gerrit more or less stopped, I am not sure if 2.8.6.1 would happen. I'll have to leave it to others to decide. (FWIW, I've been told that it's unlikely for 2.8.x to happen after 2.8.6.1.) (If we do upgrade, we should include I9a7e42e53f8c7ac746af45967beac380705a2711, which fixes bug 67866 for us)
(In reply to christian from comment #2) > Upgrade to gerrit 2.9 got WONTFIXed at bug 68271. > So, I doubt that 2.9 will happen soon for us. Ah ok, reducing scope of this bug again.
Change 150596 had a related patch set uploaded by Paladox: Upgrade gerrit to 2.8.6.1 https://gerrit.wikimedia.org/r/150596
Change 150596 abandoned by Paladox: Upgrade gerrit to 2.8.6.1 https://gerrit.wikimedia.org/r/150596
I understand that Chad is busy/fed up with gerrit and I think ops should take care of gerrit, but I don't understand what condemns us to reach the day of phabricator migration with a 15+ months old release of gerrit. 2.8.2–6 include benefits for all users, like a race condition fix, group/project list pagination, respect of MySQL hard limit, replication plugin, sshd; countless fixes for those who are using the new change screen (disclosure: I am, for performance reasons); and no changes for those who don't, AFAICS. Unless release notes lie, * there are no schema changes, * a config may need to be tweaked if we relied on default https://code.google.com/p/gerrit/issues/detail?id=2557, * no DB support is lost unless we're using MyISAM, * Bouncycastle would need to be updated if we're using it. Doesn't sound painful at first sight, though of course I'm not an op etc.
