Hi, with the future of Gerrit comes a bright future. Gerrit PolyGerrit has 
changed to Google Germany PolyGerrit team (created in january). Upstream are 
planning to ramp up development of PolyGerrit very soon. Gerrit has just had 
3.0 branched within the last 2 hours! Which means that is going to be a big 
release. Gerrit 3.0 key features are no more db's making it easier to both 
backup and fail gerrit over in case of an emergency. Another key feature is 
that PolyGerrit is now the only UI in Gerrit. The old UI has been removed!
Let's move onto 2.16.
We plan to update to Gerrit 2.16 soon [1]. With this update, it will be one of 
the largest update's to have happened to Wikimedia's Gerrit! PolyGerrit's 
becomes the default UI. PolyGerrit's UI has changed a lot since 2.15 [2]. 
PolyGerrit's UI update also include improvements for new users, such as being 
guided with a screen like [3]. The user will also be told how to update their 
own change through a dialog on their change. This may improve their experience 
and help encourage new users to contribute!
With this email, i would like to encourage all users to try out the new ui 
which you can by doing: https://gerrit.wikimedia.org/r/?polygerrit=1 or 
clicking "Switch to New UI" in the footer. Not all features are implemented 
like inline editing, project dashboard, editing of project access rules and 
more. You will find yourself needing to switch back to the OLD UI if you need 
to do any of that.
Once we switch to Gerrit 2.16, you will find your self switching virtually 
never switching to the OLD UI. Upstream (google) switched off the OLD UI last 
year and has been a great success!

[1] https://phabricator.wikimedia.org/T200739
[2] https://phabricator.wikimedia.org/F28699064 
https://phabricator.wikimedia.org/F28699068 
https://phabricator.wikimedia.org/F28699070
[3] https://phabricator.wikimedia.org/F28699002


_______________________________________________
Wikitech-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Reply via email to