- 27 Nov, 2019 1 commit
-
-
Michael Achenbach authored
https://v8.dev/blog/tags/release is the new ChangeLog! This also removes an unused file push_to_candidate.py which wasn't deleted earlier as it's intertwined a lot in test cases. This CL also cleans that up. Furthermore, logic for selecting CLs for the ChangeLog (using LOG= lines) is removed as well. Nobody has used this feature for more than 5 release cycles. We'll delete the ChangeLog file in a separate CL. Bug: v8:10010 No-Try: true Change-Id: Idee551dc0600c3df9f784cc543897e3e18517ca1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1930616Reviewed-by:
Tamer Tas <tmrts@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#65191}
-
- 20 Nov, 2019 1 commit
-
-
Dan Elphick authored
Don't overwrite WATCHLISTS each time with a checkout from the latest release branch as that means it will never pick up changes from master. No-Try: true Bug: chromium:832032 Change-Id: I3a9231369caa9a6591acb9b7f0c76dc031ab9178 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1926029 Commit-Queue: Dan Elphick <delphick@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#65063}
-
- 25 Oct, 2019 1 commit
-
-
Michael Achenbach authored
NOTRY=true Bug: chromium:1018099 Change-Id: I14de41aac11220fedb58cda9bf5ce66424ff381c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1879932Reviewed-by:
Tamer Tas <tmrts@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#64557}
-
- 19 Feb, 2019 1 commit
-
-
Vadim Gorbachev (bmsdave) authored
There are now less that 400 days until the end of life of Python 2(aka _legacy_ Python) https://pythonclock.org/ . The code compatibility check for python2 and python3 used the following tools: futurize, flake8 You can see the reports here: https://travis-ci.com/bmsdave/v8/builds This CL was uploaded by git cl split. Bug: v8:8594 Change-Id: I661c52a70527e8ddde841fee6d4dcba282b4a938 Reviewed-on: https://chromium-review.googlesource.com/c/1470123 Commit-Queue: Sergiy Belozorov <sergiyb@chromium.org> Reviewed-by:
Sergiy Belozorov <sergiyb@chromium.org> Cr-Commit-Position: refs/heads/master@{#59675}
-
- 07 Dec, 2018 1 commit
-
-
Michael Achenbach authored
Gerrit seems to concatenate several commit messages on uploading branch creation CLs. Now we pass the commit message of the branch commit to the upload script to prevent this. NOTRY=true Bug: v8:8546 Change-Id: Ia4673261aad2f40bcda4384889a0428039adae74 Reviewed-on: https://chromium-review.googlesource.com/c/1367454Reviewed-by:
Sergiy Belozorov <sergiyb@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#58092}
-
- 16 Oct, 2018 1 commit
-
-
Michael Achenbach authored
TBR=sigurds@chromium.org NOTRY=true Bug: v8:8310 Change-Id: I83b250ffa89deb59fc10434806db25893ffed375 Reviewed-on: https://chromium-review.googlesource.com/c/1282564Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#56664}
-
- 19 Sep, 2018 1 commit
-
-
Sergiy Byelozyorov authored
R=machenbach@chromium.org Bug: chromium:878303, chromium:877964 Change-Id: I9f0de35780861f3f121daa9952af70b332c11e98 Reviewed-on: https://chromium-review.googlesource.com/1231176Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Sergiy Byelozyorov <sergiyb@chromium.org> Cr-Commit-Position: refs/heads/master@{#56041}
-
- 27 Aug, 2018 1 commit
-
-
Michael Achenbach authored
TBR=mslekova@chromium.org NOTRY=true Bug: chromium:877964 Change-Id: Ia7ea1094ea339f6e956cb7241f7d35913b7821b2 Reviewed-on: https://chromium-review.googlesource.com/1190502Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#55430}
-
- 06 Jul, 2017 1 commit
-
-
Michael Achenbach authored
https://chromium-review.googlesource.com/561001 was not sufficient, because we don't use the --gerrit flag in V8 anymore. Now we explicitly pass an option for private upload. TBR=hablich@chromium.org,tandrii@chromium.org NOTRY=true Bug: v8:6574 Change-Id: Ib8e2883795f26f22ac47e648b37c47f3a0a60a40 Reviewed-on: https://chromium-review.googlesource.com/561378Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#46439}
-
- 03 Jul, 2017 2 commits
-
-
Michael Achenbach authored
The release tools used to reload CL descriptions from rietveld to consider late edits. This makes no sense anymore with gerrit, so we drop the feature. NOTRY=true TBR=hablich@chromium.org Bug: chromium:685318 Change-Id: I08231795ba3b25c0939aa2b4428973086548484d Reviewed-on: https://chromium-review.googlesource.com/558915Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#46389}
-
Michael Achenbach authored
This uploads roll-branch CLs before landing and fixes an ambiguity bug when pushing tags. NOTRY=true TBR=hablich@chromium.org Bug: chromium:738679 Change-Id: I51e03d714ec97ee2d9bca4ecaf753d66038891c1 Reviewed-on: https://chromium-review.googlesource.com/558415Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#46382}
-
- 15 Dec, 2016 1 commit
-
-
machenbach authored
This splits branch ref creation and landing. The ref now directly uses heads (without pending) and for landing we use depot_tools. For simplicity, the check for existing tags is removed, as it now is very unlikely to happen again without gnumbd. BUG=chromium:674448 NOTRY=true TBR=tandrii@chromium.org Review-Url: https://codereview.chromium.org/2584523002 Cr-Commit-Position: refs/heads/master@{#41716}
-
- 13 Apr, 2016 3 commits
-
-
machenbach authored
TBR=hablich@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/1885863003 Cr-Commit-Position: refs/heads/master@{#35442}
-
machenbach authored
Fix after https://codereview.chromium.org/1887583002/ TBR=hablich@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/1881163003 Cr-Commit-Position: refs/heads/master@{#35441}
-
machenbach authored
Check if a previous run left an inconsistent state behind. The check is right before trying to push a new state as then all information is available, like commit message and tag name. This is still only a band-aid. If gnumbd is down for a longer period, an unprocessed commit won't be found, but the push attempt will still fail. Review URL: https://codereview.chromium.org/1887583002 Cr-Commit-Position: refs/heads/master@{#35437}
-
- 04 Feb, 2016 1 commit
-
-
hablich authored
With the combination of the WATCHLISTS feature and create_release.py it is possible to notify the mailing list v8-merges@googlegroups.com on pending merges. On master this notification is deactivated. R=machenbach@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/1663003003 Cr-Commit-Position: refs/heads/master@{#33719}
-
- 06 Mar, 2015 1 commit
-
-
machenbach authored
This makes now the same simplification as the chromium release scripts do. For creating branch B from a gnumbd'ed (aka real) commit X do: 1. Branch Y off the real X 2. Set refs/pending/heads/B to Y 3. Set refs/pending-tags/B to X 4. Set refs/heads/B to X The old algorithm tried to branch off the pending correspondent of X. That commit was determined by comparing tree objects of the real X and commits on pending. Unfortunately, multiple commits on one branch can refer to the same tree object, e.g., for commits P, Q, R with R being the revert of Q, P and R refer to the same tree object. TBR=tandrii@chromium.org NOTRY=true TEST=./script_test.py TEST=tools/release/create_release.py -a me -r you --dry-run Review URL: https://codereview.chromium.org/979243004 Cr-Commit-Position: refs/heads/master@{#27042}
-
- 12 Feb, 2015 1 commit
-
-
machenbach authored
This is needed as normal chromium checkouts don't fetch branch-heads. These branches will also be replicated by GitHub and are fetched when cloning from the repository. The expected object size will be the same or smaller than before as we currently push the same information onto the candidates branch (which already is in refs/heads). The only difference is the increasing number of refs in refs/heads. BUG=chromium:451975 TBR=tandrii@chromium.org NOTRY=true LOG=n TEST=./script_test.py TEST=tools/release/create_release.py -r machenbach@chromium.org -a machenbach@chromium.org --dry-run Review URL: https://codereview.chromium.org/914973002 Cr-Commit-Position: refs/heads/master@{#26629}
-
- 30 Jan, 2015 1 commit
-
-
machenbach authored
BUG=chromium:451975 TBR=tandrii@chromium.org NOTRY=true LOG=n TEST=./script_test.py TEST=tools/release/create_release.py -r machenbach@chromium.org -a machenbach@chromium.org --dry-run Review URL: https://codereview.chromium.org/881683004 Cr-Commit-Position: refs/heads/master@{#26364}
-