Skip to content
This repository has been archived by the owner on Nov 29, 2022. It is now read-only.

docs: update Cadence Pause blog post with electron 9 release #3770

Merged
merged 9 commits into from May 11, 2020

Conversation

sofianguy
Copy link
Contributor

@sofianguy sofianguy commented Mar 30, 2020

To be in sync with Chromium, we have decided to move our Electron 9 stable date to Chromium's M83 stable date, May 19th.

ref electron/electron#22863

data/blog/cadence-pause.md Outdated Show resolved Hide resolved
sofianguy and others added 2 commits March 30, 2020 16:56
Co-Authored-By: Mark Lee <malept@users.noreply.github.com>
@malept
Copy link
Member

malept commented Mar 31, 2020

Should we also mention something along the lines of "Moving forward, we will be basing stable releases on odd-numbered Chromium releases" ?

@malept malept changed the title doc: update Cadence Pause blog post with electron 9 release docs: update Cadence Pause blog post with electron 9 release Mar 31, 2020
@sofianguy
Copy link
Contributor Author

I think we can omit that details to give us leeway in future release dates

Copy link
Member

@erickzhao erickzhao left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we also update the "Electron is temporarily pausing major releases" tagline to reflect the fact that we have a confirmed delayed date?

From the main https://www.electronjs.org/blog page, that's the only sentence that's immediately visible above the fold.

@sofianguy
Copy link
Contributor Author

@erickzhao good call. maybe we can add a line under that with something like "edit (2020-04-01): Electron 9 stable will be released on May 19th, 2020" ?

@codebytere codebytere merged commit 4a60c22 into electron:master May 11, 2020
@sofianguy sofianguy deleted the patch-2 branch May 11, 2020 21:28
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants