Fixed
Status Update
Comments
mi...@google.com <mi...@google.com> #2
[Empty comment from Monorail migration]
da...@gmail.com <da...@gmail.com> #3
Discussed in yesterday's meeting. More details will come in the minutes which will be published on the project home page soon.
[Monorail components: ESC]
[Monorail components: ESC]
ma...@gmail.com <ma...@gmail.com> #4
[Empty comment from Monorail migration]
ma...@gmail.com <ma...@gmail.com> #5
Humble thank you from me, for working on this.
hi...@google.com <hi...@google.com> #6
[Empty comment from Monorail migration]
al...@google.com <al...@google.com> #7
Done last November. The tentative roadmap for Gerrit is available at https://www.gerritcodereview.com/roadmap.html .
ek...@google.com <ek...@google.com> #8
[Monorail components: SteeringCommittee]
ek...@google.com <ek...@google.com> #9
[Monorail components: -ESC]
ek...@google.com <ek...@google.com> #10
[Empty comment from Monorail migration]
is...@google.com <is...@google.com> #11
Edits were made to reflect the following in Monorail: auto-CCs.
Description
Since many parties are involved with Gerrit, this roadmap should be open so that everyone can contribute to it.
Besides transparency we also hope to foster collaboration when the roadmap is public. E.g. if it's known that a big party will work on a certain topic, others that are interested in this topic may be able to join and help with implementing some of the pieces.
Maintaining a roadmap, a release plan and a prioritized backlog is a responsibility of the Engineering Steering Committee [1]. This is why I will suggest to put this on the agenda for the next ESC meeting.
[1]