Hi Erik, Merging decisions are up to the Chrome Release team (or the Security Team for security fixes). You can always request a merge (by adding a Merge-Request-xyz label to the bug), and argue why you think it should be done, and see what they decide. Make sure to tag the bug with the right OS label, otherwise it won't get looked at. ChromeOS does care about older branches, they even backport security patches to their LTS releases that don't get refreshes on other OSs any more.
(Also, I think there's a typo in the first line of your mail: when Chrome 130 goes to stable, then V8 *12.9* usually doesn't get updated any more. V8 *13.0* does definitely get security fixes throughout its lifetime as a stable release.) Does that answer your question? Cheers, Jakob On Mon, Oct 14, 2024 at 4:33 PM Erik Corry <[email protected]> wrote: > Hi > > I can see at https://chromiumdash.appspot.com/schedule that Chrome stable > is going to version 130 tomorrow, and normally that would mean no more > security updates for V8 version 13.0. > > But on the other hand there are another two weeks before version 130 goes > to ChromeOS, so does that mean there will be security updates on V8 version > 12.9 in the intervening period? > > -- > Erik Corry > -- -- v8-dev mailing list [email protected] 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-dev/CAKSzg3T0G8oTTK6pXL2MVugPVSJRv%3Dy5OjhZMOa8PaAr23jc0A%40mail.gmail.com.
