See also: T280: [EPIC] Code Deploy Dashboard, which is more and different than this, but related.

And some tasks have multiple patches associated with them, which also makes the meaning of the release tags unclear.

Gerrit shows the list of including branches nowadays, which tells you whether something is deployed as long as you remember the current WMF branch names, but it would be still nice to have something that is understandable to the average user.

This may now be possible as polygerrit is built from js and html not java a lot more people can contribute to do this :).

We could get them to support doing this from a polygerrit plugin which will use polymer template which is very extendable :)

With PolyGerrit we could develop a plugin that display deployment status right above the file list. Would need some kind of rest api or json file where we could parse.

Within Gerrit, the "Included In" section already indicates which branches a change was naturally a part of.

However, this could also be realised on the Phabricator side. Per T229934: Enable semantic relationship between code review changesets and maniphest tasks in phabricator (show "Related Gerrit Patches"), @mmodell has implemented the following:

To resolve this task, perhaps it could be extended to, in addition to the branch it was merged into, also the newest deploy/release branch it is a part of. E.g. to display at most one "wmf/*" or "REL*" (the newest one), falling back to "master" (or whatever the repo's head branch is). E.g. it would show "master" for stuff landed just now, "1.35-0.wmf.5" for stuff that's in prod already, and "REL1_34" (or 1.34.x) for stuff that's been in prod longer and and released already.

In T88136#5648060, @Krinkle wrote:

To resolve this task, perhaps it could be extended to, in addition to the branch it was merged into, also the newest deploy/release branch it is a part of. E.g. to display at most one "wmf/*" or "REL*" (the newest one), falling back to "master" (or whatever the repo's head branch is). E.g. it would show "master" for stuff landed just now, "1.35-0.wmf.5" for stuff that's in prod already, and "REL1_34" (or 1.34.x) for stuff that's been in prod longer and and released already.

That sounds pretty reasonable, however, due to our practice of cherry-picking changes to release branches, I think that each copy of a patch will get its own row in the "related gerrit patches" table. I could filter or group the table to get the behavior you described but as it stands now it should be easy to determine where a patch was merged since it will be listed once for each cherry-picked copy of the patch.

Yeah, for cherry-picks it would be separate at first. I think that's okay for now (not required to resolve the immediate need). At least the information will be in the table somewhere. Perhaps we could make it slightly easier by sorting the rows in a way that makes them next to each other (e.g. sort by Change-Id first, then by last-mod as now). That way we don't need a new concept for "grouping" yet.