Moving some offtopic discussion from the other report:

>>! In T65847#1268528, @Florian wrote:
> Gerrit [[ https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.11.html | release 2.11 ]] adds another really really useful feature, [[ https://gerrit-documentation.storage.googleapis.com/Documentation/2.11/user-inline-edit.html | inline editing ]], which allows you to create changes within the browser without cloning the repo or checkout the change itself. I know, that we're planing to migrate gerrit to phabricators Differential, but it would be a very nice and (like i said) useful feature in gerrit, which (as far as i know) doesn't exist in Differential at the moment (see {T409}, and it seems, see the discussion on the upstream task, that this feature will not arrive in Differential in the next time). In my point of view it would be a step backwards if Gerrit now (after a long long time of user wishes, i think) get's a web based editor and we move to Differential, which doesn't support this feature and doesn't has the plan to implement it.
> 
> Another point is, that i don't see a real roadmap for the migration (i read some tasks and haven't found one to implement a testing environment to show the code-review process, which wasn't resolved so far and was planned for last xyear september iirc, but i doesn't find it again :/). So, should we re-consider to upgrade gerrit? That would make it possible to resolve {T71445}.
> 
> But there is a (maybe) bad thing with Gerrit 2.11: The old (actual default) change screen was removed iirc, so the new change screen is the default, see for information https://gerrit-review.googlesource.com/Documentation/user-review-ui.html.



>>! In T65847#1268589, @matmarex wrote:
>> But there is a (maybe) bad thing with Gerrit 2.11: The old (actual default) change screen was removed iirc, so the new change screen is the default
> 
> Good, it's already way better than the old one in the ancient beta version we're running, and I heard that the issues it has got ironed out. I'd also love if the upgrade (any upgrade) happened.



>>! In T65847#1268589, @matmarex wrote:
>> But there is a (maybe) bad thing with Gerrit 2.11: The old (actual default) change screen was removed iirc, so the new change screen is the default
> 
> Good, it's already way better than the old one in the ancient beta version we're running, and I heard that the issues it has got ironed out. I'd also love if the upgrade (any upgrade) happened.



>>! In T65847#1268606, @Florian wrote:
>>>! In T65847#1268584, @JanZerebecki wrote:
>> I'd like the upgrade to 2.11 to be reconsidered. But it is also a question of finding someone who does the work. So lets first find someone to do the work of upgrading to 2.8.6.1.
> 
> Not really needed, we're already using gerrit release 2.8.x (2.8.1), which would allow us to directly upgrade to 2.11, see https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.11.html
> 
> (let's adjust the title of this task to "Upgrade gerrit", because it seems, that we are currently not really sure, _if_ we can/should/want upgrade gerrit at all :))
> 
> 
> 
>>>! In T65847#1268589, @matmarex wrote:
>>> But there is a (maybe) bad thing with Gerrit 2.11: The old (actual default) change screen was removed iirc, so the new change screen is the default
>> 
>> Good, it's already way better than the old one in the ancient beta version we're running, and I heard that the issues it has got ironed out. I'd also love if the upgrade (any upgrade) happened.
> 
> +1, i tested it locally and it's a big improvement, still a "new" thing, but you find all needed things very fast :)