Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to chromium-dev
Hi, fellow developers!
What?
We have deprecated support for Android 6.0 Marshmallow, API level 23, in the Chromium code base. The minimum version supported going forward is Android 7.0 Nougat, API level 24.
* Regarding cronet: The parts of the code base that affect cronet still need to support older versions of Android (supported cronet builders listed here).
Why?
We value our users and want to keep them safe on the web, but maintaining Chrome on operating system versions that are no longer supported reduces our ability to move the rest of Chrome forward. As other apps have done, we have decided to end support for Android 6.0 Marshmallow now that
almost 7 years have passed since its final update.
When?
Chrome M106 is the last release that will support Android 6.0 Marshmallow. You can find the
Chrome release schedule here.
Chrome M107 will not be shipped to Android 6.0 Marshmallow so you can now make cleanups for this on the main branch.
For cleanup CLs related to this, you can either use this meta bug: https://crbug.com/1363002, or file blocking bugs.
--
The Chrome team at Google
Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Tommy Nyquist, chromium-dev
This is exciting! But M106 doesn't go stable for another ~2 weeks. Should we wait 2 weeks to ensure we don't make cherry-picks more risky?
Also - I think we can't bump our
default_min_sdk_version, or remove API guards for M until our android-marshmallow trybots are updated (or else break the trybots)?
Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to nyq...@chromium.org, chromium-dev
Hi folks,
We are glad to share the news that Android Marshmallow CQ builders[1][2] have been replaced by a new CQ builder on Android Nougat (android-nougat-x86-rel) on the main branch.
Next steps will include:
Make the CQ switch for M107 branch.
Removing Marshmallow from sheriffing tools for main and M107 branches: (Tracking bug).
Submitting a change to increase the minimum SDK version for main (and possibly M107 branch).
After that we expect cleanup to start in earnest. For details, please check all the open tickets in the "BlockedOn" field of the meta bug.
Should you have any questions, please feel free to reply to this email or create blocking bugs.
Thanks,
The Chrome team at Google.
--
Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Andrew Grieve, chromium-dev
Haiyang Pan unread, Nov 21, 2022, 8:16:49 PM11/21/22 Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to chromium-dev
Hello everyone,
It has been a month since we started migrating the builders affected by the Marshmallow deprecation. Here is a quick update on where we are right now.
TL;DR; For chromium builders that run test on devices:
15 builders have been migrated or removed.
4 are working in progress.
3 are not started yet.
Here is the detailed information.
Thanks,
The Chrome team at Google.
--
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3