Old, unprocessed commits erroneously display "This change has not been released" |
|||||
Issue descriptionI would like to know what milestone shipped r474450. I tried: https://chromiumdash.appspot.com/commit/12dedc4fa09fc54ee6d0bd54d7ffde5c5ab2bdba which redirects me to: https://chromiumdash-staging.googleplex.com/commit/12dedc4fa09fc54ee6d0bd54d7ffde5c5ab2bdba due to issue 791697. But the staging instance says: This change has not been released. which is clearly false, because the change landed eight months ago.
,
Jan 31 2018
,
Jan 31 2018
,
Mar 2 2018
> We should probably either (1) backfill further if possible or (2) at least indicate that the data isn't available, but point out that the change has definitely been released. Agree. I was trying to find 87a6cd117134638 and was irritated to see "has not been released", whereas https://storage.googleapis.com/chromium-find-releases-static/87a.html#87a6cd117134638915c862592b1b4c8c00e4b7c6 indicates the version correctly.
,
Mar 2 2018
,
Apr 4 2018
We've processed all commits from M61+. so, everything should now be consistent. And also updated a more meaning full message for unprocessed commits. "Release information is not available for commits that shipped prior to M61." Please refer to crbug.com/817043 |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by amineer@chromium.org
, Jan 31 2018Summary: Old, unprocessed commits erroneously display "This change has not been released" (was: chromiumdash-staging missing release info?)