diff options
author | hcm <hcm@google.com> | 2016-02-23 16:26:03 -0800 |
---|---|---|
committer | Commit bot <commit-bot@chromium.org> | 2016-02-23 16:26:03 -0800 |
commit | 85a7a5fc6c2528f05eeaa18e1c359fbaed724d3d (patch) | |
tree | 4ee9929a4e5f9f73ef1a043dfe5c5e29130f2685 /site/schedule.md | |
parent | 69c1b24bcaa7cffd59753a75a7f3d155696fcac4 (diff) |
Skia schedule on skia.org
BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search2?unt=true&query=source_type%3Dgm&master=false&issue=1726253002
NOTRY=true
DOCS_PREVIEW= https://skia.org/?cl=1726253002
TBR=reed@google.com
Review URL: https://codereview.chromium.org/1726253002
Diffstat (limited to 'site/schedule.md')
-rw-r--r-- | site/schedule.md | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/site/schedule.md b/site/schedule.md new file mode 100644 index 0000000000..7ac1c4cf81 --- /dev/null +++ b/site/schedule.md @@ -0,0 +1,24 @@ +Milestone Schedule +================== + +On a six week cadence aligned with Chromium, Skia cuts milestone branches. +Clients wishing to stay on a relatively stable level of Skia often utilize these +branches. + +On the branch date, a healthy level of Skia near HEAD is chosen. After this +point, for the next six weeks, only high priority fixes are checked into the branch. +After the six week period, when another branch is cut, only critical (typically +security) fixes will be committed to any previous branch. + +Skia 2016 schedule: + + Milestone | Branch Date (end of day) + ----------|------------------------- + 50 | 02/25/16 + 51 | 04/07/16 + 52 | 05/19/16 + 53 | 06/30/16 + 54 | 08/25/16 + 55 | 10/06/16 + 56 | 11/17/16 + |