On Mon, Nov 15, 2010 at 08:44, Mads Sig Ager <[email protected]> wrote:
> there is no separate release notification for V8 at this point. We > branch V8 at the same time as Chromium and I therefore don't think > that a separate notification is needed? > Does it mean that stable V8 is one that ships with stable Chromium and so on (just checking)? Even then, I think Linux distributions (and possibly other projects) are interested in V8 as a package independent from Chromium (for example, to use it with nodejs or mongodb). It's not just a theoretical thing. Users are asking distros for V8 packages and V8 support in existing packages like mongodb. Currently it's non-trivial to determine the version of V8 used for any given version of Chromium (one has to either download and run the browser to see about:version, or look into src/v8/version.cc for given release; the latter is inconvenient, because only DEPS files for releases are tagged). It would be great to at least include the V8 version number in the Chromium release notes (I have asked for that in the past). Furthermore, it would be useful to have separate security notifications for V8, because it may be maintained for distros by different people (this seems to be the case with above Red Hat bug). If you're going to say that other projects using V8 should just bundle it, note that many of the arguments above still apply. The people bundling V8 would like to know which version is considered stable, they would like to know when to update their bundled copy, and they better update it when there are security issues. And then, it is useful to make V8 distro-friendly because then distros will do most of the above for people, making it easier to write software using V8 (at least on Linux). -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
