docs: add 2020-04-15 release wg notes (#270)
This commit is contained in:
Родитель
5c6c8279ff
Коммит
14bc283793
|
@ -0,0 +1,43 @@
|
|||
# Releases WG
|
||||
|
||||
### Date: 2020-04-15
|
||||
|
||||
## Attendees
|
||||
|
||||
**Members**
|
||||
* @codebytere
|
||||
* @ckerr
|
||||
* @zcbenz
|
||||
* @deepak1556
|
||||
* @jkleinsc
|
||||
* @MarshallOfSound
|
||||
* @sofianguy
|
||||
|
||||
**Visitors**
|
||||
|
||||
## Agenda
|
||||
|
||||
- (@alexeykuzmin) [#21256 Accessing `document.cookie` in preload script will break cookies after navigating to a new URL](https://github.com/electron/electron/issues/21256)
|
||||
* This is a real regression and it affects Teams among other apps.
|
||||
* All `7.x.y` and `8.x.y` releases are affected.
|
||||
* This is an upstream issue with Chromium, for which there exist workarounds
|
||||
* **Verdict:** We will wait and confirm with Alexey before proceeding
|
||||
* Issue triage schedule
|
||||
* Do we want to rotate issue triage to make sure it's done more reliably?
|
||||
* Let's take a roll call for who would be interested in performing issue triage on a semi-regular basis
|
||||
* Note: this does not mean necessarily solving, simply adding labels and perhaps determining if it's a reasonable issue for us to solve or closable based on lack of actionable outcomes.
|
||||
* Spicy pepper schedule?
|
||||
* https://electronhq.slack.com/archives/CUWPAN8AX/p1586902566006000
|
||||
* **Verdict:** Tentatively schedule Electron v11 for quiet release.
|
||||
|
||||
## Backport Requests
|
||||
|
||||
* [Pending votes](https://github.com/electron/electron/pulls?q=is%3Apr+is%3Aopen+label%3A%22pending-vote+🗳%22)
|
||||
|
||||
## Action Items
|
||||
|
||||
- @codebytere to take a roll call for who would be interested in performing issue triage on a semi-regular basis
|
||||
|
||||
## Follow-Up Discussion
|
||||
|
||||
|
Загрузка…
Ссылка в новой задаче