On 2026-10-10 9:40 PM, Gordon Messmer wrote:
If the Electron package maintains release parity, then every 8 weeks
its maintainers need to introduce a new package, deprecate an old
package, update three releases of the Electron package, and make sure
that all of the packages that rely on Electron have been rebuilt
against an actively supported release. We'll also end up with two
Electron runtimes that don't have upstream maintenance of the Chromium
codebase, which is... not great.
For what it's worth, I'll retract that statement.
I've (locally) built Electron 43.8.3, and it looks like once Chromium
stops publishing releases, the Electron developers start cherry-picking
patches including security fixes:
https://github.com/electron/electron/commits/43-x-y/patches
That being the case, I don't think there's any security basis for
keeping just one Electron release in Fedora, and the only real
limitation we have is available labor.
If anyone wants to learn to maintain an Electron release, let me know.
--
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://forge.fedoraproject.org/infra/tickets/issues/new
