chore: quiet period blog post 24 #685
Open
+34
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ckerr
reviewed
Nov 21, 2024
|
|
||
| The Electron project will pause for the month of December 2024, then return to full speed in January 2025. | ||
|
|
||
| <iframe src="https://giphy.com/embed/3otPoSDQczp1s9kVAQ" width="480" height="259" style="" frameBorder="0" class="giphy-embed" allowFullScreen></iframe><p><a href="https://giphy.com/gifs/filmeditor-disney-pixar-3otPoSDQczp1s9kVAQ">via GIPHY</a></p> |
|
|
||
| ## What will be different in December | ||
|
|
||
| 1. Final stable branch releases of Electron 31, 32, and 33 will occur the week of December 1st. There will be no additional planned releases in December. |
There was a problem hiding this comment.
The phrasing here makes it sound like we're EOLing 31, 32, and 33 😱
Suggested change
| 1. Final stable branch releases of Electron 31, 32, and 33 will occur the week of December 1st. There will be no additional planned releases in December. | |
| 1. No new stable releases are planned between December 8 and 31st. |
There was a problem hiding this comment.
Oh, I definitely meant for that to be "Final stable branch releases of Electron 31, 32, and 33 for 2024 will occur the week of December 1st. " I think the original with that modification could be fine instead, but your edit does allow us to decide not to release new stables the week of December 1st if we decide not to.
VerteDinde
approved these changes
Nov 21, 2024
Comment on lines
+20
to
+23
| 1. Zero-day and other major security-related releases will be published as necessary. Security | ||
| incidents should be reported via [SECURITY.md](https://github.com/electron/electron/tree/main/SECURITY.md). | ||
| 1. [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) reports | ||
| and moderation will continue. |
There was a problem hiding this comment.
Suggested change
| 1. Zero-day and other major security-related releases will be published as necessary. Security | |
| incidents should be reported via [SECURITY.md](https://github.com/electron/electron/tree/main/SECURITY.md). | |
| 1. [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) reports | |
| and moderation will continue. | |
| 1. Zero-day and other major security-related releases will be published as necessary. Security | |
| incidents should be reported via [SECURITY.md](https://github.com/electron/electron/tree/main/SECURITY.md). | |
| 2. [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) reports | |
| and moderation will continue. |
Not sure why GitHub didn't apply the 2 here
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.