-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roll dartium to Chromium 45 #24218
Comments
Shouldn't this be labeled milestone 1.13? @mit-mit was not aware of this work, and its impact on the release? |
Also, what is the schedule for this work? We are just a week from cherry pick season. |
Per leads meeting discussion, this is not in 1.13. Marking for 1.14. |
Moving to 1.15 per leads discussion. The work is almost complete, and should land in a 1.15 dev channel release soon, however we want a bit more "bake time" before we put it in a stable release. |
Can we close this? I believe this is in bleeding edge now, right? CC @whesse |
Yes. There is some further work, about the SDK and IDL generation, but a separate bug should be filed for that, and it won't be milestone 1.15. I'll leave it to Terry to close this. |
Clearing out 1.15 milestone as the last full push to dev has happened. If any changes are required before 1.15 is shipped, please file a merge request |
Closing this bug as the roll shipped in 1.15. @terrylucas @kevmoo can you open a new issue(s) tracking what remains in 1.16? |
These are the Active Dartium 1.16 bugs On Thu, Mar 10, 2016 at 12:53 AM, Michael Thomsen notifications@github.com
|
Excellent, thanks Terry! |
No description provided.
The text was updated successfully, but these errors were encountered: