1Milestone Schedule
2==================
3
4On a six week cadence aligned with Chromium, Skia cuts milestone branches.
5Clients wishing to stay on a relatively stable level of Skia often utilize these
6branches.
7
8On the branch date, a healthy level of Skia near HEAD is chosen.  After this
9point, for the next six weeks, only high priority fixes are checked into the branch.
10After the six week period, when another branch is cut, only critical (typically
11security) fixes will be committed to any previous branch.
12
13Skia 2017 schedule:
14
15  Milestone | Branch Date (beginning of day)
16  ----------|-------------------------------
17  57        | 01/19/17
18  58        | 03/02/17
19  59        | 04/13/17
20  60        | 05/25/17
21  61        | 07/20/17
22  62        | 08/31/17
23  63        | 10/12/17
24  64        | 11/30/17
25
26The current milestone is included in the headers in
27[SkMilestone.h](https://skia.googlesource.com/skia/+/master/include/core/SkMilestone.h).
28