V8 versions supports

[Meir Shpilraien]

Hey,

According to the documentation, around every 4 weeks a new stable version is tagged and the maintenance of the previous version is stopped. This is why we should make sure we are always up to date with the latest stable version:

https://v8.dev/docs/release-process#which-version-should-i-embed-in-my-application%3F

That said, I saw that chromeOS has a long term support version which is released every six month. Assuming I take the V8 version which ship with this LTS version of chromeOS, can I assume that I will get patches on this V8 version on critical bugs and security fixes?

I am asking because I want to understand my options about upgrade requirements.

Thanks,

Meir.

[Lutz Vahl]

Hi Meir,

Yes, roughly every 4 weeks we're shipping a new V8 release version which will be included in the relevant chromium build. You can find the full schedule online: https://chromiumdash.appspot.com/schedule

Once the version is not shipped to stable users any more, we'll stop merging patches.

In addition ChromeOS is maintaining a V8 LTS version. Only platform specific patches will be applied to this version, so I've you're planning to use V8 outside of ChromeOS you might lag patches. Therefore I'd not recommend using this V8 version.

Feel free to reach out if you have any questions.

Cheers,

 Lutz

Lutz Vahl

Technical Program Manager, Chrome Web Platform

Google Germany GmbH

Erika-Mann-Strasse 36

80636 München

Geschäftsführer: Paul Manicle, Liana Sebastian

Registergericht und -nummer: Hamburg, HRB 86891

Sitz der Gesellschaft: Hamburg

Diese E-Mail ist vertraulich. Falls Sie diese fälschlicherweise erhalten haben sollten, leiten Sie diese bitte nicht an jemand anderes weiter, löschen Sie alle Kopien und Anhänge davon und lassen Sie mich bitte wissen, dass die E-Mail an die falsche Person gesendet wurde. 

     

This e-mail is confidential. If you received this communication by mistake, please don't forward it to anyone else, please erase all copies and attachments, and please let me know that it has gone to the wrong person.

Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

--
--
v8-dev mailing list
v8-...@googlegroups.com
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to v8-dev+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/v8-dev/62e1a216-24b5-4a3e-bab7-6f22bbf65028n%40googlegroups.com.

[Ben Noordhuis]

On Sun, Oct 22, 2023 at 11:32 AM Meir Shpilraien <me...@redis.com> wrote:
>

Another option is to track Node.js's "fork" of V8. We maintain our
copy in deps/v8 for as long as the corresponding node release branch
is maintained. E.g. the v20 branch gets support until April 2026.

Caveat emptor w.r.t. security fixes: node's threat model differs from
chromium in that executed code = trusted code. Local exploits are not
prio-drop-everything like they are for chromium.