Skip to content
This repository has been archived by the owner on Jan 10, 2023. It is now read-only.

Automatically determine which release a feature shipped in #6

Open
maxh opened this issue Jun 9, 2014 · 0 comments
Open

Automatically determine which release a feature shipped in #6

maxh opened this issue Jun 9, 2014 · 0 comments

Comments

@maxh
Copy link
Contributor

maxh commented Jun 9, 2014

We should:

  1. Extract crbug numbers from the original intent emails
  2. Monitor those crbugs for revisions landing
  3. Correlate the revision numbers with the cut numbers tracked here http://omahaproxy.appspot.com/viewer
  4. Update the "Release" column in bit.ly/blinkintents
@maxh maxh changed the title Automatically determine which release a milestone shipped in Automatically determine which release a feature shipped in Jun 9, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant