-
-
Notifications
You must be signed in to change notification settings - Fork 67
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
[Feature]: Google Chrome 'Early' Stable Release #562
Comments
Evergreen is using the channels feed provided by Google. I don't think that Google publishes an early stable as a channel: (irm -uri "https://versionhistory.googleapis.com/v1/chrome/platforms/win64/channels").channels | fl
name : chrome/platforms/win64/channels/extended
channelType : EXTENDED
name : chrome/platforms/win64/channels/stable
channelType : STABLE
name : chrome/platforms/win64/channels/beta
channelType : BETA
name : chrome/platforms/win64/channels/dev
channelType : DEV
name : chrome/platforms/win64/channels/canary
channelType : CANARY
name : chrome/platforms/win64/channels/canary_asan
channelType : CANARY_ASAN |
For reference, here's what Evergreen currently returns: $ Get-EvergreenApp GoogleChrome | ft
Version Architecture Channel Type URI
------- ------------ ------- ---- ---
118.0.5993.54 x64 beta msi https://dl.google.com/dl/chrome/install/beta/googlechromebetastandaloneenterprise64.msi
118.0.5993.54 x86 beta msi https://dl.google.com/dl/chrome/install/beta/googlechromebetastandaloneenterprise.msi
120.0.6050.0 x86 canary exe https://dl.google.com/update2/installers/ChromeSetup.exe
119.0.6034.6 x64 dev msi https://dl.google.com/dl/chrome/install/dev/googlechromedevstandaloneenterprise64.msi
119.0.6034.6 x86 dev msi https://dl.google.com/dl/chrome/install/dev/googlechromedevstandaloneenterprise.msi
116.0.5845.228 x64 extended msi https://dl.google.com/dl/chrome/install/googlechromestandaloneenterprise64.msi
116.0.5845.228 x86 extended msi https://dl.google.com/dl/chrome/install/googlechromestandaloneenterprise.msi
118.0.5993.54 x64 stable msi https://dl.google.com/dl/chrome/install/googlechromestandaloneenterprise64.msi
118.0.5993.54 x64 stable zip https://dl.google.com/dl/chrome/install/GoogleChromeEnterpriseBundle64.zip
118.0.5993.54 x86 stable msi https://dl.google.com/dl/chrome/install/googlechromestandaloneenterprise.msi |
Yes apologies Evergreen does currently offer all 5 Channels (So I've updated my original text above) |
Unfortunately there's no release date in the update feed - that would be ideal. There may be a secondary feed that could be use to find the dates. |
What is your feature request?
Currently Google have 5 release channels, (Chrome browser release channels) - Stable, Extended stable, Beta, Dev and Canary - Evergreen offers all of these.
Last December Google published the following Blog Change in release schedule from Chrome 110 this details their plan to do an 'Early Stable Release' - approx 6 days before the Stable Release was published - it infers this will fundamentally be the same product.
The challenge as we have found today (Friday 6th October) is a new Early Stable Release has been published (v
118.0.5993.54), this is the first time I am aware of this happening since the Blog linked above was published, We have discovered this is published in the Stable Release Channel.
We are hesitant to deploy this to all devices
If you see the RSS Feed from Google (I've attached a screen grab below), they do appear to differentiate between 'Early Stable Release' (Early Stable Update for Desktop in screen grab) and 'Stable Release' (Stable Channel Update for Desktop in screen grab):
So this feature request is sort of a change to how Evergreen works to allow us as admins to grab the appropriate version to allow us to manage who we deploy the Early Stable release to and who remains on the current Stable release.
I am aware what I'm asking may not be possible without Google specifically creating a new 6th channel e.g. 'Early Stable Channel', but... Can Evergreen be modified to somehow differentiate between a Stable Release and an Early Stable Release?
Thanks in Advance.
Have you tested against the current version?
Have you reviewed the documentation?
The text was updated successfully, but these errors were encountered: