Hi Wilfried,

you can also have a look 
at https://code.google.com/p/v8-wiki/wiki/ReleaseProcess which describes 
the point of the different types of branches.

Cheers,
Michael

On Wednesday, July 29, 2015 at 5:40:10 PM UTC+2, Jakob Kummerow wrote:
>
> On Wed, Jul 29, 2015 at 5:09 PM, Wilfried Gösgens <[email protected] 
> <javascript:>> wrote:
>
>> Ok, 
>> looking at...
>> https://gist.github.com/domenic/aca7774a5d94156bfcc1
>> would give me this URL:
>> https://chromium.googlesource.com/v8/v8.git/+/branch-heads/4.1 
>>
>
> How does it "give you" 4.1? It tells you to use the same branch as stable 
> Chrome, no? Which is 4.4, as I've said before.
>  
>
>> which reads:
>>
>> Version 4.1.0.27 (cherry-pick)
>>
>> Correct, that's the tip of the 4.1 branch.
>
>> But git only shows me versions with 3.xx and 4.2.xx, 4.3.xx, 4.5.xx and 
>> 4.6.xx?
>>
>>
> Huh?
> $ git log -1 --pretty=oneline branch-heads/4.1
> 901b67916dc2626158f42af5b5c520ede8752da2 Version 4.1.0.27 (cherry-pick)
>
>> Whats the point in having a 3 pages long Readme
>>
>> Huh? What 3-pages long Readme? 
>
> *Look at the V8 version x.y.z.w of Chrome-Stable on omahaproxy.com 
> <http://omahaproxy.com> (second-to-last column), take the "x.y" part and 
> plug it into chromium.googlesource.com/v8/v8.git/+/branch-heads/x.y 
> <http://chromium.googlesource.com/v8/v8.git/+/branch-heads/x.y>. *
>
> Done, that's it. If even that is too long for your taste, use this 
> approximation:
>
> *Look at the V8 version x.y.z.w of Chrome-Stable on omahaproxy.com 
> <http://omahaproxy.com>.*
>
>>  how to find out which is a release instead of having a wiki page with 
>> '1.5.2015 V8 release xyz, maintained until 15.6.2015'? 
>>
>> Because that wiki page would both be more verbose than the one-liner 
> above, and quite boring to update every six weeks. 
>
> Being a long time Contributor to citadel.org and libical, we also got 
>> down to doing something like this - Even with a changelog listing the 
>> features.
>>
>> Reading the GIST, I guess (once more..) the last stable release before 
>> 3.31.74.1 was 3.29.88.19 ?
>>
>
> Nope, there was a branch-heads/3.30 in between those two. But don't use 
> that, it's outdated, it has known security/stability bugs which will never 
> be patched. (You seem to think that 3.x is somehow better than 4.x. It's 
> not. Not more stable either. Just more outdated.)
>  
>
>>
>> On Wednesday, July 29, 2015 at 3:54:26 PM UTC+2, Jakob Kummerow wrote:
>>>
>>> On Wed, Jul 29, 2015 at 2:50 PM, Wilfried Gösgens <[email protected]> 
>>> wrote:
>>>
>>>> Hm, that explains a lot.
>>>> Its pretty hard to tell what actually _is_ a v8 release and what not. 
>>>>
>>>
>>> In an open source world, every commit is a "release". We happen to 
>>> create 1-3 daily snapshots that have version numbers, mostly to make it 
>>> easier to talk about them.
>>>  
>>>
>>>> The closest thing I could find was browse 
>>>> http://omahaproxy.appspot.com/ - 
>>>>
>>>
>>> Could have searched this list, would have found e.g. 
>>> https://groups.google.com/forum/#!topic/v8-users/RkobpinkoKM with 
>>> detailed instructions and examples.
>>>  
>>>
>>>> and whenever all 'stable' columns point to the same version, thats a 
>>>> release.
>>>>
>>>
>>> Picking whatever is shipping in Chrome-stable is a reasonable rule of 
>>> thumb. (Stable versions for Linux/Mac/Windows should always be in sync; 
>>> CrOS and Android often lag behind a few days.)
>>>  
>>>
>>>> Is there a better way? and which was the next stable release after 
>>>> 3.31.74.1?
>>>>
>>>
>>> The stable branch you're asking for is branch-heads/4.1, but note that 
>>> this, too, has reached its end of life months ago. The currently supported 
>>> stable branch is branch-heads/4.4. Every branch has a support period of 6 
>>> weeks, there are no long-term support branches or anything like that.
>>>  
>>>
>>>>
>>>> On Wednesday, July 29, 2015 at 2:24:31 PM UTC+2, Jakob Kummerow wrote:
>>>>>
>>>>> 3.31.74.1 was a failed attempt at creating a sufficiently stable basis 
>>>>> for a branch point, and is totally unsupported. Pretty bad idea to use 
>>>>> that 
>>>>> in production. I'm not surprised it's crashing.
>>>>>
>>>>>>
>>>>>> --- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "v8-users" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>> send an email to [email protected].
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>
>>>>>
>>>
>

-- 
-- 
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to