Skip to content

V
V8
Switch branch/tag
  1. 03 Dec, 2015 1 commit
  3. 27 Apr, 2015 1 commit
  5. 16 Apr, 2015 1 commit
  7. 15 Apr, 2015 1 commit
  9. 07 Apr, 2015 2 commits
  11. 14 Mar, 2015 1 commit
  13. 05 Mar, 2015 1 commit
    • machenbach's avatar
      Make auto-roller roll recent release based on timestamp. · a6a0bd88
      machenbach authored 
      Before this change, out of two versions 4.2.13.1 and
4.2.14, the latter would have been considered the newest.
Now, the timestamp of the commit determines the age, which
allows to roll a patched version first. The auto-roller
will only roll forward (i.e. there needs to be a commit
range between the last roll and the new candidate).

Additionally, this CL does some cleanups:
- Use the sheriff detection mechanism in the auto-roller.
- Require the roll revision parameter in the chromium_roll
script to avoid redundancy. The auto_roll script determines
that revision automatically.
- Simplify the revision summary in the commit message. The
summary will now show last_roll..new_roll, which e.g.
includes the version change CL. It'll now show useful
information for cherry-picks, which it didn't before.
- Remove unused clusterfuzz check. That check is part of the
release process script.

TBR=tandrii@chromium.org
NOTRY=true
TEST=./script_test.py
TEST=./tools/release/chromium_roll.py --dry-run --sheriff -c ~/tmp/chromium/src --last-roll 55b9049ea3978a589d8db2aa191d21222eef737f fc263505535a175c8efa18f4c787bd92a1d1ab3d --use-commit-queue -r me -a you

Review URL: https://codereview.chromium.org/977903002

Cr-Commit-Position: refs/heads/master@{#27009}
      a6a0bd88
  15. 16 Feb, 2015 1 commit
    • machenbach's avatar
      Fix v8rel script after adding roll branches. · b351e302
      machenbach authored 
      Use git hashes as keys when referring to releases, not
pure commit position numbers as those are not unique.

Better bailout to only check for recent releases.

Add new branching method with a roll branch in heads to
the v8rel test case.

Fix the way v8 is referred to in DEPS files in the test
cases. The test still had svn-number style.

BUG=chromium:451975
TBR=tandrii@chromium.org
NOTRY=true
LOG=n

TEST=./script_test.py

Review URL: https://codereview.chromium.org/928243002

Cr-Commit-Position: refs/heads/master@{#26669}
      b351e302
  17. 29 Jan, 2015 1 commit
  19. 26 Jan, 2015 2 commits
    • machenbach's avatar
      External name changes of release scripts. · ae22d7f8
      machenbach authored 
      Moved and renamed the scripts to fit with git.

These changes require documentation updates, updates of
the release spreadsheet and the buildbot side.

BUG=chromium:451975
TBR=tandrii@chromium.org
NOTRY=true
LOG=n

Review URL: https://codereview.chromium.org/868473004

Cr-Commit-Position: refs/heads/master@{#26271}
      ae22d7f8
    • machenbach's avatar
      Clean up release scripts. · 379dcd5b
      machenbach authored 
      This makes some internal renaming, e.g. trunk -> candidates,
bleeding edge -> master, without changing the api.

Also remove some unused bailout steps from the push script.

Remove unused bump version script.

BUG=chromium:451975
TBR=tandrii@chromium.org
NOTRY=true
LOG=n

Review URL: https://codereview.chromium.org/873213002

Cr-Commit-Position: refs/heads/master@{#26269}
      379dcd5b
  21. 14 Nov, 2014 1 commit
  23. 12 Nov, 2014 1 commit
  25. 05 Nov, 2014 1 commit
  27. 30 Oct, 2014 1 commit
  29. 16 Oct, 2014 1 commit
  31. 13 Oct, 2014 1 commit
  33. 25 Sep, 2014 1 commit
  35. 23 Sep, 2014 2 commits
  37. 19 Sep, 2014 1 commit
  39. 05 Sep, 2014 1 commit
  41. 04 Sep, 2014 1 commit
  43. 25 Aug, 2014 1 commit
  45. 22 Aug, 2014 1 commit
  47. 28 Jul, 2014 1 commit
  49. 16 Jul, 2014 1 commit
    • machenbach@chromium.org's avatar
      Add script to bump up version on bleeding edge. · 570ea3bf
      machenbach@chromium.org authored 
      The version.cc file will from now on be controlled on
bleeding edge and on trunk. The next version to use will
always be max(bleeding_edge_version, trunk_version) + 1.

The trunk and bleeding_edge versions are not semantically
tied together. The trunk branch can be used to make
independent point releases of bleeding_edge revisions.

The version on bleeding_edge will be increased if:
- the lkgr version is smaller than the version of the latest
  revision,
- the lkgr version is not a version change itself,
- the tree is not closed for maintenance.

This will allow chromium to refer directly to bleeding_edge
revisions of v8. The v8 versions will not be unique, but
they will change as often as possible, dependent on the lkgr
cycle time and the frequency this script is called.

BUG=391261
LOG=n
TEST=tools/push-to-trunk/script_test.py
TEST=tools/push-to-trunk/bump_up_version.py --dry_run
R=jarin@chromium.org

Review URL: https://codereview.chromium.org/389353003

git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22421 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      570ea3bf
  51. 05 May, 2014 1 commit
  53. 25 Apr, 2014 1 commit
  55. 15 Apr, 2014 1 commit
  57. 14 Apr, 2014 1 commit
  59. 11 Apr, 2014 1 commit
  61. 09 Apr, 2014 1 commit