| OLD | NEW |
| 1 You want to be very careful about updating the reference builds, because it | 1 You want to be very careful about updating the reference builds, because it |
| 2 means changing the baseline all new builds are compared to on the performance | 2 means changing the baseline all new builds are compared to on the performance |
| 3 graphs and can easily let regressions slip in. | 3 graphs and can easily let regressions slip in. |
| 4 | 4 |
| 5 | 5 |
| 6 The Chromium and Google Chrome builds the same revisions so you can compare | 6 The Chromium and Google Chrome builds the same revisions so you can compare |
| 7 Google Chrome and Chromium performance data. | 7 Google Chrome and Chromium performance data. |
| 8 | 8 |
| 9 | 9 |
| 10 For the Chromium build, just take a build off the waterfall's continuous | 10 For the Chromium build, just take a build off the waterfall's continuous |
| (...skipping 16 matching lines...) Expand all Loading... |
| 27 svn remove Chromium.app/Contents/Versions/[old_version] | 27 svn remove Chromium.app/Contents/Versions/[old_version] |
| 28 | 28 |
| 29 b. Anything with a status of "?" you need to svn add (usually the new | 29 b. Anything with a status of "?" you need to svn add (usually the new |
| 30 version directory is the only thing). Remember to use --no-ignore so | 30 version directory is the only thing). Remember to use --no-ignore so |
| 31 any binary files svn might try to ignore get included (.so, .dylib, | 31 any binary files svn might try to ignore get included (.so, .dylib, |
| 32 etc.). | 32 etc.). |
| 33 | 33 |
| 34 svn add --no-ignore Chromium.app/Contents/Versions/[new_version] | 34 svn add --no-ignore Chromium.app/Contents/Versions/[new_version] |
| 35 | 35 |
| 36 | 36 |
| 37 Since there usually isn't an official build with exact same revsion, you have | 37 Since there usually isn't an official build with exact same revsion, |
| 38 to do that yourself ("branding=Chrome buildtype=Official"). | 38 you have to do that yourself ("branding=Chrome buildtype=Official"). |
| 39 You must build the official build on a Mac OS X 10.5 machine, unless |
| 40 we started building the official builds on Mac OS X 10.6 (see |
| 41 http://crbug.com/38443). |
| 39 | 42 |
| 40 | 43 |
| 41 Once the build is done, remove the keystone framework and plist keys so when | 44 Once the build is done, remove the keystone framework and plist keys so when |
| 42 it is used by tests, it won't try to keep itself updated. | 45 it is used by tests, it won't try to keep itself updated. |
| 43 | 46 |
| 44 rm -rf \ | 47 rm -rf \ |
| 45 "Google Chrome.app/Contents/Versions/[new_version]/Google Chrome Frame
work.framework/Frameworks/KeystoneRegistration.framework" | 48 "Google Chrome.app/Contents/Versions/[new_version]/Google Chrome Frame
work.framework/Frameworks/KeystoneRegistration.framework" |
| 46 | 49 |
| 47 From both the app and framework Info.plist: | 50 From both the app and framework Info.plist: |
| 48 | 51 |
| 49 "Google Chrome.app/Contents/Info.plist" | 52 "Google Chrome.app/Contents/Info.plist" |
| 50 "Google Chrome.app/Contents/Versions/4.0.287.0/Google Chrome Framework.f
ramework/Resources/Info.plist" | 53 "Google Chrome.app/Contents/Versions/4.0.287.0/Google Chrome Framework.f
ramework/Resources/Info.plist" |
| 51 | 54 |
| 52 remove the Keystone entries: | 55 remove the Keystone entries: |
| 53 | 56 |
| 54 KSVersion | 57 KSVersion |
| 55 KSProductID | 58 KSProductID |
| 56 KSUpdateURL | 59 KSUpdateURL |
| 57 | 60 |
| 58 | 61 |
| 59 Then repeat the rsync/svn remove/svn add steps that were done with the Chromium | 62 Then repeat the rsync/svn remove/svn add steps that were done with the Chromium |
| 60 app, but with the Google Chrome app instead. | 63 app, but with the Google Chrome app instead. |
| 61 | 64 |
| 62 | 65 |
| 63 Finally commit these changes and you'll then need to roll src/DEPS to to pull | 66 Finally commit these changes and you'll then need to roll src/DEPS to to pull |
| 64 in the new reference builds. | 67 in the new reference builds. |
| OLD | NEW |