says "Chromium will also continue to exist as it always has, without any RLZ library included. And, you can still download a Google Chrome with no RLZ behavior at www.google.com/chrome. But now that RLZ is open, Google Chrome distributed through promotional means will include this open-source implementation of RLZ.".
So what makes the continuous Chromium build a "Google Chrome distributed through promotional means"?
> What makes the continuous Chromium build a "Google Chrome distributed through promotional means"?
The continuous builders exist to compile and test all the code. Therefore they build with RLZ options enabled.
The continuous build binaries are literally whatever the state of the tree happened to be at the time. They're useful for bisection but people aren't expected to run them for non-development reasons.
Well that's very misleading, even Wikipedia thinks that : " Google confirmed that the RLZ tracking token [...] [is] not in versions of Chrome downloaded from the Google website directly or in any versions of Chromium."
From the thread: "We think that the reported RLZ ping behavior (that request to "/tools/pso/ping...") is a regression -- RLZ pings should not be happening in Chromium or non-promotional Google Chrome builds, so this is not the intended behavior."
http://blog.chromium.org/2010/06/in-open-for-rlz.html
says "Chromium will also continue to exist as it always has, without any RLZ library included. And, you can still download a Google Chrome with no RLZ behavior at www.google.com/chrome. But now that RLZ is open, Google Chrome distributed through promotional means will include this open-source implementation of RLZ.".
So what makes the continuous Chromium build a "Google Chrome distributed through promotional means"?