| 43 | | WebKitGTK and WPE WebKit share stable branches, maintained under [https://trac.webkit.org/browser/webkit/releases/WebKitGTK webkit/releases/WebKitGTK]. (For historical reasons, we don't use the branches directory for our branches.) Maintaining a stable branch is a lot of work, and deciding which commits to backport is not always easy. Our goal is to backport fixes for bugs, without accidentally backporting patches that introduce new bugs, but this is sometimes easier said than done. In general, backporting more patches increases the risk of regressions, so it requires care. In addition to backporting patches proposed for backport on the [https://trac.webkit.org/wiki/WebKitGTK/StableRelease#Listofreleases stable branch wiki pages], we've successfully used two different strategies to identify other commits that should be backported. |
| | 43 | WebKitGTK and WPE WebKit share stable branches, maintained under [https://trac.webkit.org/browser/webkit/releases/WebKitGTK webkit/releases/WebKitGTK]. (For historical reasons, we don't use the branches directory for our branches.) Maintaining a stable branch is a lot of work, and deciding which commits to backport is not always easy. Our goal is to backport fixes for bugs without accidentally backporting patches that introduce new bugs, but this is sometimes easier said than done. In general, backporting more patches increases the risk of regressions, so it requires care. In addition to backporting patches proposed for backport on the [https://trac.webkit.org/wiki/WebKitGTK/StableRelease#Listofreleases stable branch wiki pages], we've successfully used two different strategies to identify other commits that should be backported. |
