https://bugzilla.wikimedia.org/show_bug.cgi?id=63847

Nemo <federicol...@tiscali.it> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|                            |https://code.google.com/p/g
                   |                            |errit/issues/list?can=1&q=l
                   |                            |abel%3AFixedIn-2.8.4+OR+lab
                   |                            |el%3AFixedIn-2.8.3+OR+label
                   |                            |%3AFixedIn-2.8.2+OR+label%3
                   |                            |AFixedIn-2.8.5+OR+label%3AF
                   |                            |ixedIn-2.8.6&colspec=ID+Typ
                   |                            |e+Stars+Milestone+Status+Pr
                   |                            |iority+Owner+Summary&cells=
                   |                            |tiles
            Summary|Upgrade gerrit to 2.8.5+    |Upgrade gerrit to 2.8.6

--- Comment #6 from Nemo <federicol...@tiscali.it> ---
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to