docs/release_process.md - Issue 1459823002: [Docs] Removed unused docs because they are moved to GitHub

Side by Side Diff: docs/release_process.md

Issue 1459823002: [Docs] Removed unused docs because they are moved to GitHub (Closed) Base URL: https://chromium.googlesource.com/v8/v8.git@master

Patch Set: Created 5 years, 1 month ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

OLD	NEW
	(Empty)
1 # Introduction

2

3 The V8 release process is tightly connected to [Chrome's](https://www.chromium.o rg/getting-involved/dev-channel). The V8 team is using all four Chrome release c hannels to push new versions to the users.

4

5 If you want to look up what V8 version is in a Chrome release you can check [Oma haProxy](https://omahaproxy.appspot.com/). For each Chrome release a separate br anch is created in the V8 repository to make the trace-back easier e.g. for [Chr ome 45.0.2413.0](https://chromium.googlesource.com/v8/v8.git/+/chromium/2413).

6

7 # Canary releases

8 Every day a new Canary build is pushed to the users via [Chrome's Canary channel ](https://www.google.com/chrome/browser/canary.html?platform=win64). Normally th e deliverable is the latest, stable enough version from [master](https://chromiu m.googlesource.com/v8/v8.git/+/roll).

9

10 Branches for a Canary normally look like this

11

12 ```

13 remotes/origin/4.5.35

14 ```

15

16 # Dev releases

17 Every week a new Dev build is pushed to the users via [Chrome's Dev channel](htt ps://www.google.com/chrome/browser/desktop/index.html?extra=devchannel&platform= win64). Normally the deliverable includes the latest stable enough V8 version on the Canary channel.

18

19 Branches for a Dev normally look like this

20

21 ```

22 remotes/origin/4.5.35

23 ```

24

25 # Beta releases

26 Roughly every 6 weeks a new major branch is created e.g. [for Chrome 44](https:/ /chromium.googlesource.com/v8/v8.git/+log/branch-heads/4.4). This is happening i n sync with the creation of [Chrome's Beta channel](https://www.google.com/chrom e/browser/beta.html?platform=win64). The Chrome Beta is pinned to the head of V8 's branch. After approx. 6 weeks the branch is promoted to Stable.

27

28 Changes are only cherry-picked onto the branch in order to stabilize the version .

29

30 Branches for a Beta normally look like this

31

32 ```

33 remotes/branch-heads/4.5

34 ```

35

36 They are based on a Canary branch.

37

38 # Stable releases

39 Roughly every 6 weeks a new major Stable release is done. No special branch is c reated as the latest Beta branch is simply promoted to Stable. This version is p ushed to the users via [Chrome's Stable channel](https://www.google.com/chrome/b rowser/desktop/index.html?platform=win64).

40

41 Branches for a Stable normally look like this

42

43 ```

44 remotes/branch-heads/4.5

45 ```

46

47 They are promoted (reused) Beta branches.

48

49 # Which version should I embed in my application?

50

51 The tip of the same branch that Chrome's Stable channel uses.

52

53 We often backmerge important bug fixes to a stable branch, so if you care about stability and security and correctness, you should include those updates too -- that's why we recommend "the tip of the branch", as opposed to an exact version.

54

55 As soon as a new branch is promoted to Stable, we stop maintaining the previous stable branch. This happens every six weeks, so you should be prepared to update at least this often.

56

57 Example: The current stable Chrome release is [44.0.2403.125](https://omahaproxy .appspot.com), with V8 4.4.63.25. So you should embed [branch-heads/4.4](https:/ /chromium.googlesource.com/v8/v8.git/+/branch-heads/4.4). And you should update to branch-heads/4.5 when Chrome 45 is released on the Stable channel.

OLD	NEW

« no previous file with comments | « docs/profiling_chromium_with_v8.md ('k') | docs/runtime_functions.md » ('j') | no next file with comments »