从2021年9月开始，Electron将每8周发布一个新的主要稳定版本。

---

2019年，Electron 改为12周的发布周期，以匹配 Chromium 的6周发布周期。 最近，Chrome 和 Microsoft 都发生了一些变化，使得我们重新考虑更改 Electron 目前的发布频率：

1. Chromium 计划从2021年9月21日的 Chrome 94 开始每4周发布一个新的里程碑。此版本节奏还每8周添加新的"扩展稳定"选项，其中包含所有更新的安全修补程序。

2. 微软应用商店要求 基于Chromium应用的版本号不得低于最新发行版本2个版本号。 例如，如果最新发布的Chromium主版本号为85，任何基于Chromium的应用其所用版本必须为83或更高。 以上规则包含Electron应用。

从2021年9月开始，Electron将每8周发布一个新的主要稳定版本，以匹配Chromium的8周扩展稳定版本。

我们的第一个发行版Electron 15将会随Chromium扩展稳定版在2021年9月21日释出。

需要注意的是，版本发行频率的改变会影响下游应用程序的开发，我们想让我们的开发者社区尽快知晓此次改变。 请阅读我们的2021开发计划以获取更多详情。

Electron 15：临时 Alpha 内测版本​

基于我们的Electron15初始版本针对的是Chromium的非扩展稳定版(其扩展稳定版基于偶数版本号)，我们需要改变我们的初始目标发行日期。 然而，一款Electron的app必须使用最近两个版本以内的Chromium以便能被微软商店收录，这项新规定会使得等待两个新版本变得不可持续。

伴随着这两项要求，我们的团队也面临着时间规划上的挑战。 推进Electron 15以包括Chromium的M94版本会使得应用开发者们能快速获取最新的Chromium扩展稳定版；然而这也会使得公测版到稳定版的开发周期缩短到只有3周。

为了有利于此次变动，Electron将会提供一个临时的内测版本，并仅限于Electron 15系列的发行版。 本内测版将给与开发者们更多时间，用这款比每日版更稳定的版本去测试和规划他们的Eletron15。

Electron 15系列内测版本频道将会于2021年7月21日开通。 It will transition to a beta release on September 1st, 2021 with a stable release target of September 21st, 2021. 在那之后的Electron发行版将不再包含内测系列。

2021 发行计划​

以下是我们当前的2021发行计划:

Electron	Chrome	Alpha 版本	Beta 版本	Stable 版	Stable 发布周期(周数)
E13	M91	-	2021年3月5日	2021年5月25日	12
E14	M93	-	2021年5月26日	2021年8月31日	14
E15	M94	2021年7月20日	2021年9月01日	2021年9月21日	9周(包含 alpha 版本)
E16	M96	-	2021年9月22日	2021年11月16日	8
E17	M98	-	2021年11月17日	2022年2月1日	11

添加 alpha 通道将 Electron 15 发布前的开发时间从 3 周延长到 9 周 - 更接近我们新的 8 周周期，同时仍满足 Windows 应用商店提交的要求。

为了进一步帮助应用程序开发人员， 从2021年的剩余时间到2022年5月，我们还将把我们支持的版本政策从最新的3个版本扩展到最新的4个版本的Electron。 这意味着即使您无法立即更改升级计划，旧版本的Electron仍将收到安全更新和修复程序。

解决疑虑​

在安排此发布周期更改之前，我们发布这篇文章是有原因的。 我们知道，更快的发布周期将对Electron应用程序产生真正的影响 - 其中一些应用程序可能已经认为我们的主要发布节奏过于频繁。

我们试图解决以下常见问题：

❓ 为什么要做这样的改变？ 为什么不保持12周的发布节奏呢？​

为了在Electron中提供最新版本的Chromium，我们的发布计划需要跟踪他们的版本。 有关Chromium发布周期的更多信息可以在这里找到 。

此外，目前12周的发布节奏将无法满足Microsoft应用商店的新提交要求。 即使是最新稳定版本的Electron上的应用程序也会经历大约两周的时间，他们的应用程序根据新的安全要求可能会被拒绝。

每个新的 Chromium 版本都包含新的功能，错误修复/安全修复和V8 改进。 作为应用程序开发人员，我们希望你们及时做出这些更改，所以我们的稳定版本日期将继续与其他Chromium稳定版本保持一致。 作为应用程序开发人员，您将比以前更快地获得Chromium和V8的新功能和修复程序。

❓ 现有的12周发布计划已经进展很快。 团队正在采取哪些步骤来简化升级？​

更频繁发版的一个好处是发版内容_更少_ 。 我们知道升级Electron的主版本可能是困难的。 我们希望较小的版本将减少每个版本中 Chromium和Node 重大更改，以及更少的破坏性改动。

❓ 未来的 Electron 版本会提供 alpha 版本吗？​

目前没有支持永久性的 Alpha 版本的计划。 此 Alpha 仅适用于 Electron 15，作为帮助开发人员在较短的发布周期内更轻松升级的一种方式。

❓ Electron 会扩展支持的版本数量吗？​

随着 Electron 19 的发布，我们将支持的版本政策从 Electron 的最新三个版本扩展到最新的四个版本直到 2022 年 5 月。 在 Electron 19 发布后，我们将返回 支持最新的三个主版本，以及 beta 和 nightly 版本。

E13 (2021年5月)	E14 (2021年8月)	E15 (2021年9月)	E16 (2021年11月)	E17 (2022年2月)	E18 (2022年3月)	E19 (2022年5月)
13.x.y	14.x.y	15.x.y	16.x.y	17.x.y	18.x.y	19.x.y
12.x.y	13.x.y	14.x.y	15.x.y	16.x.y	17.x.y	18.x.y
11.x.y	12.x.y	13.x.y	14.x.y	15.x.y	16.x.y	17.x.y
--	--	12.x.y	13.x.y	14.x.y	15.x.y	--

问题?​

📨 您有任何问题或疑虑，请发送邮件至 info@electronjs.org 或加入我们的Discord。 我们知道这是一个将影响许多应用程序和开发者的变化，您的反馈对我们非常重要。 我们希望收到您的来信！

At OpenJS World this morning, we announced that Electron has officially graduated from the OpenJS Foundation's incubation program, and is now an OpenJS Foundation Impact Project.

Electron entered incubation in December of 2019, at the last OpenJS Foundation global conference in Montreal. We're excited to take a larger role in the JavaScript community as an Impact Project, and continue our partnership with the OpenJS Foundation.

---

Learning more​

You can read up on the foundation, its mission, and its members on the OpenJSF website. The OpenJS Foundation is host to a number of open source JavaScript projects including jQuery, Node.js, and webpack. It's supported by 30 corporate and end-user members, including GoDaddy, Google, IBM, Intel, Joyent, and Microsoft.

Electron is an open–source framework for building cross-platform desktop applications with web technologies. To learn more about the humans behind Electron and how they work together, take a look at our Governance page.

To get started with Electron itself, take a peek at our documentation.

Electron 正在暂停更新大型版本

---

发生了什么？​

我们的 大型更新时间表 与Chromium 同步更新，Chromium项目最近由于调整工作时间表已决定 暂停更新。 这意味着，在Chromium经过改变的更新节奏期间，Electron也会暂时性地暂停重大更新。

我们认为，我们的最佳选择是沿着Chromium的脚步走下去， 因此，在过渡时期，Electron团队将转为全天候处理错误、安全、性能和稳定性问题。

我们希望确保我们的维护者和消费者的福利在这个时候都得到优先考虑。 因此，我们欢迎你们的反馈，并期待着恢复我们的正常发布时间表。

欲了解更多更新信息，请关注我们的 Twitter。

编辑(2020-03-30)：Election 9 稳定版将针对Chromium M83，并于2020年5月19日发布。 这针对 Chromium的声明 关于跳过M82稳定日期并调整M83稳定版发布日期。

At Node+JS Interactive in Montreal, the OpenJS Foundation announced that it accepted Electron into the Foundation's incubation program. The Foundation is committed to supporting the healthy growth of the JavaScript ecosystem and web technologies by providing a neutral organization to host and sustain projects, as well as collaboratively fund activities for the benefit of the community at large.

The OpenJS Foundation is host to a number of open source JavaScript projects including jQuery, Node.js, and webpack. It's supported by 30 corporate and end-user members, including GoDaddy, Google, IBM, Intel, Joyent, and Microsoft. Electron is an open–source framework for building cross-platform desktop applications with web technologies.

This is an exciting move for Electron, and we see it as a next step in our evolution as an open-source project.

---

What this means for developers​

Electron joining the OpenJS Foundation does not change how Electron is made, released, or used — and does not directly affect developers building applications with Electron. Even though Electron was originally created at GitHub in 2013, it is currently maintained by a number of organizations and individuals. In 2019, Electron codified its governance structure and invested heavily into formalizing how decisions affecting the entire project are made. We believe that having multiple organizations and developers investing in and collaborating on Electron makes the project stronger.

Lifting Electron up from being owned by a single corporate entity and moving it into a neutral foundation focused on supporting the web and JavaScript ecosystem is a natural next step as we mature as an open-source project.

Learning more​

You can read up on the foundation, its mission, and its members on the OpenJSF website. For more information and quotes about the acceptance of Electron into the OpenJSF incubation program, check out the official press release. To learn more about the humans behind Electron and how they work together, take a look at our Governance page.

To get started with Electron itself, take a peek at our documentation.

🎉 Electron 每12周将会新发布一个稳定版本！ 🎉

---

⚡️ 哇，那也太快了！ 但为什么呢？​

简而言之，Chromium 不会停止发布新版本，所以 Electron 的研发也不会减速。

Chromium 的发布遵循每六周更新一次的规划。 为了在Electron中提供最新版本的Chromium，我们的发布计划需要跟踪他们的版本。 有关Chromium发布周期的更多信息可以在这里找到 。

🚀 为什么是每12周一次？​

每6周，新的 Chromium 版本就会发布新功能，错误 / 安全修复和 V8 的改进。 Electron 用户一直迫切明确地表示希望这些更改能及时进行，因此我们调整了稳定发布日期，以匹配其他所有Chromium 稳定版本。 首先，Electron v6.0.0 将包括 M76，并计划于2019年7月30日发布稳定版，与Chromium M76同一天发布。

🚧这对我和我的 Electron 应用意味着什么？​

您将能比以前更快地访问新的 Chromium 和 V8 功能和补丁。 重要的是，_当这些新变化到来时_您也能知道，因此您将能够使用比以前更好的信息进行规划。

Electron 团队 将继续支持 最新的三个主要版本。 例如，当 v6.0.0 在 2019 年 7 月 30 日稳定时，我们将继续支持 v6.x、v5.x 和 v4.x，而 v3.x 将寿终正寝。

💬 应用反馈项目​

请考虑加入我们的 应用反馈计划 ，以帮助我们测试 Beta 版和应用稳定性。 Projects who participate in this program test Electron betas on their apps; and in return, the new bugs they find are prioritized for the stable release.

📝 Electron 版本简史​

在 v3.0.0 之前，有关稳定版本的发布决策没有规律进行。 我们添加了项目的内部时间表与 v3.0.0 和 v4.0.0。 今年早些时候，我们决定首次发布 Electron v5.0.0 的稳定发布日期。 总的来说，宣布我们的稳定发布日期得到了积极的回应，我们很高兴在未来的版本中继续这样做。

为了更好地简化这些与升级相关的工作，我们的更新和发布工作组将会和我们的治理组合作 他们使得我们能够更好地确定这项工作的优先级并委派这项工作，我们希望在后续的版本中这些改变都会变得更加明显。

以下是我们和 Chromium 相比的更新计划表：

📨 如果您有任何疑问，请发送电子邮件至 info@electronjs.org。

As Electron grows in popularity for desktop applications, the team working on it has also grown: we have more fulltime maintainers who work for different companies, live in different timezones, and have different interests. We're introducing a governance structure so we can keep growing smoothly.

---

Why are things changing?​

People in the Electron project coordinate in timezones around the world with volunteers, with full-time maintainers, and with several companies who all rely on Electron. Until now, we've been successful with informal coordination; but as the team has grown, we've found that the approach doesn't scale. We also want to make it easier for new contributors to find a place to call home in the project.

工作组​

Electron governance includes working groups that are responsible for different parts of the project. We're starting out with seven groups:

• Community & Safety: Handles Code of Conduct issues.
• Docs & Tooling: Oversees externally-focused tooling (e.g. Fiddle, Forge) and the Electron documentation.
• Outreach: Helps grow the Electron community.
• Releases: Ensures releases are stable and on schedule.
• Security: Performs security testing and responds to security issues.
• Upgrades: Integrates upstream upgrades, such as new versions of V8, Chromium, and Node.
• Website: Maintains and improves the Electron website.

These groups will coordinate with each other, but each has their own meeting schedules and agendas to be productive on their own. More details on these groups are available at the governance repository.

Does this change the Electron project's direction?​

This shouldn't have any direct effect on Electron's direction. If our strategy is successful, working groups will make it easier for new contributors to find topics that interest them, and make maintainers' lives simpler by moving discussion unrelated to their day-to-day work to other groups. If that happens, it may indirectly affect things by having more unblocked people working together.

Where can I learn more?​

• The governance repo and charter have information about the new governance structure.
• Each working group has its own page: Community, Docs & Tools, Outreach, Releases, Security, Upgrades, and Website.
• You can contact the maintainers by opening an issue or mailing us at info@electronjs.org.

Electron 团队将停止支持 32 位 Linux (ia32 / i386)，从Electron v4.0 开始。 支持基于32位的 Linux 安装的 Electron 最后版本是 Electron v3.1，它将获得支持版本直到Electron v6 被解除。 Support for 64-bit based Linux and armv7l will continue unchanged.

---

What exactly is Electron no longer supporting?​

You may have seen the description "64-bit" and "32-bit" as stickers on your computer or as options for downloading software. The term is used to describe a specific computer architecture. Most computers made in the 1990s and early 2000s were made with CPUs that were based on the 32-bit architecture, while most computers made later were based on the newer and more powerful 64-bit architecture. The Nintendo 64 (get it?) and the PlayStation 2 were the first widely available consumer devices with the new architecture, computers sold after 2010 contained almost exclusively 64-bit processors. As a result, support has been shrinking: Google stopped releasing Chrome for 32-bit Linux in March 2016, Canonical stopped providing 32-bit desktop images in 2017 and dropped support for 32-bit altogether with Ubuntu 18.10. Arch Linux, elementary OS, and other prominent Linux distributions have already dropped support for the aging processor architecture.

Until now, Electron has provided and supported builds that run on the older 32-bit architecture. From release v4.0 onwards, the Electron team will no longer be able to provide binaries or support for 32-bit Linux.

Electron has always been a vibrant open source project and we continue to support and encourage developers interested in building Electron for exotic architectures.

这对开发者意味着什么？​

If you are not currently providing 32-bit distributions of your app for Linux, no action is required.

Projects which ship 32-bit Linux Electron applications will need to decide how to proceed. 32-bit Linux will be supported on Electron 3 until the release of Electron 6, which gives some time to make decisions and plans.

这对用户意味着什么？​

If you are a Linux user and not sure whether or not you're running a 64-bit based system, you are likely running on a 64-bit based architecture. To make sure, you can run the lscpu or uname -m commands in your terminal. Either one will print your current architecture.

If you are using Linux on a 32-bit processor, you have likely already encountered difficulties finding recently released software for your operating system. The Electron team joins other prominent members in the Linux community by recommending that you upgrade to a 64-bit based architecture.

If you're having trouble using a native Node.js addon with Electron 5.0, there's a chance it needs to be updated to work with the most recent version of V8.

---

Goodbye v8::Handle, Hello v8::Local​

In 2014, the V8 team deprecated v8::Handle in favor of v8::Local for local handles. Electron 5.0 includes a version of V8 that has finally removed v8::Handle for good, and native Node.js addons that still use it will need to be updated before they can be used with Electron 5.0.

The required code change is minimal, but every native Node module that still uses v8::Handle will fail to build with Electron 5.0 and will need to be modified. The good news is that Node.js v12 will also include this V8 change, so any modules that use v8::Handle will need to be updated anyway to work with the upcoming version of Node.

I maintain a native addon, how can I help?​

If you maintain a native addon for Node.js, ensure you replace all occurrences of v8::Handle with v8::Local. The former was just an alias of the latter, so no other changes need to be made to address this specific issue.

You may also be interested in looking into N-API, which is maintained separately from V8 as a part of Node.js itself, and aims to insulate native addons from changes in the underlying JavaScript engine. You can find more information in the N-API documentation on the Node.js website.

帮助! I use a native addon in my app and it won't work!​

If you're consuming a native addon for Node.js in your app and the native addon will not build because of this issue, check with the author of the addon to see if they've released a new version that fixes the problem. If not, reaching out to the author (or opening a Pull Request!) is probably your best bet.

Electron now uses GN to build itself. Here's a discussion of why.

---

GYP and GN

当Electron于2013年首次发布时，Chromium的构建配置是用 GYP编写的，短于“生成你的项目”。

2014年， Chromium项目引入了一个新的构建配置工具，叫做 GN (简称“生成 Ninja”)，Chromium的构建文件被迁移到GN ，GYP 被从源代码中删除。

Electron 历史上一直保持主 Electron 代码 和 libchromiumcontent之间的分离， 对 Chromium 的 'content' 子模块的 Electron 部分。 Electron has carried on using GYP, while libchromiumcontent -- as a subset of Chromium -- switched to GN when Chromium did.

Like gears that don't quite mesh, there was friction between using the two build systems. Maintaining compatibility was error-prone, from compiler flags and #defines that needed to be meticulously kept in sync between Chromium, Node, V8, and Electron.

To address this, the Electron team has been working on moving everything to GN. Today, the commit to remove the last of the GYP code from Electron was landed in master.

What this means for you

If you're contributing to Electron itself, the process of checking out and building Electron from master or 4.0.0 is very different than it was in 3.0.0 and earlier. See the GN build instructions for details.

If you're developing an app with Electron, there are a few minor changes you might notice in the new Electron 4.0.0-nightly; but more than likely, Electron's change in build system will be totally transparent to you.

What this means for Electron

GN is faster than GYP and its files are more readable and maintainable. Moreover, we hope that using a single build configuration system will reduce the work required to upgrade Electron to new versions of Chromium.

• It's already helped development on Electron 4.0.0 substantially because Chromium 67 removed support for MSVC and switched to building with Clang on Windows. With the GN build, we inherit all the compiler commands from Chromium directly, so we got the Clang build on Windows for free!

• It's also made it easier for Electron to use BoringSSL in a unified build across Electron, Chromium, and Node -- something that was problematic before.

Electron 1.4. 2 包含一个重要的补丁，修复了一些Smantec、GeoTrust的上游Chrome 问题。 和 Thawte SSL/TLS 证书 被错误地拒绝了从 libchromiumcontent生成时间起10周内的 Chrome 库 Electron。 在受影响的网站上使用的 证书没有问题，替换这些证书并不会做什么。

---

在 Electron 1.4.0 — 1.4.11 对使用这些受影响的 证书的站点的HTTPS 请求将在某个日期之后由于网络错误而失败。 This affects HTTPS requests made using Chrome's underlying networking APIs such as window.fetch, Ajax requests, Electron's net API, BrowserWindow.loadURL, webContents.loadURL, the src attribute on a <webview> tag, and others.

将你的应用程序升级到1.4.12以防止请求失败。

**注意：**这个版本是在 Chrome 53 版本引入的，所以早入 1.4.0 版本之前的 Electron 版本不受影响。

Impact Dates​

Below is a table of each Electron 1.4 version and the date when requests to sites using these affected certificates will start to fail.

Electron Version	Impact Date
1.3.x	不受影响
1.4.0	已经失败
1.4.1	已经失败
1.4.2	已经失败
1.4.3	12月 10日 2016年 9:00 PM PST
1.4.4	12月 10日 2016年 9:00 PM PST
1.4.5	12月 10日 2016年 9:00 PM PST
1.4.6	1月 14日 2017年 9:00 PM PST
1.4.7	1月 14日 2017年 9:00 PM PST
1.4.8	1月 14日 2017年 9:00 PM PST
1.4.9	1月 14日 2017年 9:00 PM PST
1.4.10	1月 14日 2017年 9:00 PM PST
1.4.11	2月 11日 2017年 9:00 PM PST
1.4.12	不受影响

您可以通过设置您的计算机的时钟提前来验证您的应用程序的影响日期，然后检测https://symbeta.symantec.com/welcome/是否能够成功加载。

更多資料​

您可以在以下链接阅读有关此主题、原始问题以及问题修复的更多信息：

• 什么是证书透明度？
• Symtantec knowledge base article
• Chrome issue 664177
• Chrome fix for issue 664177
• libchromiumcontent patch for issue 664177