1 2--- 3title: "Milestone Schedule" 4linkTitle: "Milestone Schedule" 5 6--- 7 8 9On a six week cadence aligned with Chromium, Skia cuts milestone branches. 10Clients wishing to stay on a relatively stable level of Skia often utilize these 11branches. 12 13On the branch date, a healthy level of Skia near HEAD is chosen. After this 14point, for the next six weeks, only high priority fixes are checked into the branch. 15After the six week period, when another branch is cut, only critical (typically 16security) fixes will be committed to any previous branch. 17 18Skia 2020 schedule: 19 20 Milestone | Branch Date (beginning of day) 21 ----------|------------------------------- 22 81 | 01/30/20 23 82 | 03/12/20 24 83 | 04/02/20* 25 84 | 05/14/20 26 85 | 06/25/20 27 86 | 08/20/20 28 87 | 10/01/20 29 88 | 11/12/20 30 31Note that 82 was abandoned by Chromium and 83 schedule moved in due to COVID-19 impact. 32Skia is maintaining 82 for our customers. Future dates are subject to change. 33 34The current milestone is included in the headers in 35[SkMilestone.h](https://skia.googlesource.com/skia/+/main/include/core/SkMilestone.h). 36 37