Issue metadata
Sign in to add a comment
|
Chromium Dash Feedback - Incorrect milestones in commit view |
||||||||||||||||||||||||
Issue descriptionThe dashboard says that most of my M64 commits have landed in 64.0.3282.29. This can't be true, as I've been submitting CLs throughout the release's dev cycle. Example: https://chromiumdash.appspot.com/commit/8a87f7e5ea0fbd62d9ce5e70d9438e709683a582 Omahaproxy says: Commit 8a87f7e5... initially landed in 64.0.3264.0
,
Mar 1 2018
Dang, sorry for the confusion. This is because we didn't go all the way back in time when determining which version shipped which commit, and it looks like for M64 we processed dev channel but not canary channel (see https://bugs.chromium.org/p/chromium/issues/detail?id=817043#c1 for details). This is why the "first release" you see is the first dev channel release, when it should be the canary release you pointed to. I'm going to dupe this into the other bug. We're evaluating whether or not we can process all versions for all channels back to a certain milestone, which should resolve this. Sorry about that! |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by pwnall@chromium.org
, Feb 28 2018