On Mon, Nov 15, 2010 at 9:03 AM, Paweł Hajdan, Jr. <[email protected]> wrote: > 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)?
Yes, at this point I think that is the best way to think of it. The main source of usage and therefore bug reports for V8 is Chromium. The branch for stable Chromium should be considered the stable version of V8. I agree that we should make it easy to package and distribute V8. I will ask to have the version number included in Chromium release notes for a start. As another data point (not sure how useful it is to you), we tag versions so you can track them here: svn ls http://v8.googlecode.com/svn/tags There have been a couple of glitches where we forgot to tag a version but we will be more careful going forward. After a branch point, only the fourth component of the version number changes. This only happens for important bug fixes. The 2.3 branch is used for Chrome 7. The 2.4 branch for Chrome 8. We will branch 2.5 for Chrome 9. Cheers, -- Mads > 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 -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
