Last modified: 2014-11-06 12:42:14 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T70271, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 68271 - Upgrade gerrit to 2.9
Upgrade gerrit to 2.9
Status: RESOLVED WONTFIX
Product: Wikimedia
Classification: Unclassified
Git/Gerrit (Other open bugs)
wmf-deployment
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-07-19 13:53 UTC by paladox2015
Modified: 2014-11-06 12:42 UTC (History)
8 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description paladox2015 2014-07-19 13:53:53 UTC
Hi please upgrade gerrit to 2.9. Reason because it includes a new design by default also fixes issue and also includes a new side by side diff please see full change log at https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.9.html
Comment 1 Andre Klapper 2014-07-19 15:06:05 UTC
I don't consider "please upgrade some software to some latest version" very useful if there are not 1) very good reasons to do this 2) urgently.
Your list above does not provide any good reasons.
Comment 2 Chad H. 2014-07-19 16:51:01 UTC
Gerrit 2.9 includes the new change screen which is worse. That's a reason not to upgrade.

Plus we're planning a Phabricator migration soon-ish. What's to gain?
Comment 3 paladox2015 2014-07-19 17:34:59 UTC
Well the new design that is an option in the current version of gerrit on wikimedia is a part of the new design but they also redesigned it complete in 2.9. It also includes a new side by side diff and also Fix truncated long lines in new side-by-side diff screen.
Comment 4 paladox2015 2014-07-19 17:36:00 UTC
It also has a new plugin for bugzilla.
Comment 5 Andre Klapper 2014-07-19 19:16:33 UTC
So if it's just some new random features with questionable gain in our usecase, I will close this as WILL NOT FIX.
Comment 6 christian 2014-07-20 21:32:21 UTC
Since people asked for more reasons, why to not upgrade:

* Search backend gets switched. And the first test I made with it some time back
  were not super solid. That might have changed in the meantime, and the old
  (=current) search system has it's warts too, but we know them, and can live
  with them. No hidden dangers there.

* At first glance, it seems there are database schema changes. Those typically
  make it hard to downgrade if something goes wrong. So the upgrade would need
  good preparation. We cannot “just try it out”.

* We'd need new plugins, since part of the functionality that was in core before
  got put into separate plugins.

* We'd need to rebuild our bugzilla integration.
Comment 7 Nemo 2014-11-06 10:09:48 UTC
(In reply to christian from comment #6)
> Since people asked for more reasons, why to not upgrade:

Thanks, that's useful. None of these points applies to 2.8.x upgrades (bug 63847), correct?

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links