Thank you. Do you have plans to improve the release process of v8? I counted at least 6 glitches just in the last few months:
http://groups.google.com/group/v8-users/browse_thread/thread/ad14d2f1afd9f7e(4 problems) http://groups.google.com/group/v8-users/browse_thread/thread/f1dc3755500af0a6(1 problem) http://groups.google.com/group/v8-users/browse_thread/thread/12c6cb0d6924e9cc(1 problem; it's the current thread) I'm going to change my tool that generates v8 tarballs to double-check version.cc. It would be nice if you could create a similar tool for v8 team that would tag a release only after verifying that version.cc matches the tag name. On Thu, Jan 20, 2011 at 08:55, Mads Sig Ager <[email protected]> wrote: > Tag fixed. Thanks. > > On Thu, Jan 20, 2011 at 7:38 AM, Paweł Hajdan, Jr. < > [email protected]> wrote: > >> Checking out v8 for 3.0.7 tag results in code that seems to be 3.0.6.1 >> version: >> >> Check with: svn cat >> http://v8.googlecode.com/svn/tags/3.0.7/src/version.cc >> >> Could you check and fix the problem? Also, if it's really broken, could >> you improve the release process so thing like this can't happen? >> >> -- >> 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 -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
