Hi all, I’ve cleaned up the OnDocs label on the Github PRs. Going forward, with the 9.x release branch, I want to test every non-trivial PR on Docs first. So, a PR that’s going to get into 9.0.x will go through the following steps:
Review / commit on master branch. Set Milestone to 10.0.0, Project to 9.0.x (or 9.1.x etc.) The RMs will review the proposals for the LTS branch projects. Unreasonable requests are rejected or moved to a future release. PRs that are reasonable will get an “OnDocs” label, and we will apply / build / run with these PRs for a least a few days. Once deemed stable, such PRs will be cherry-picked by the RMs. Do *not* do this yourself, or make new PRs unless asked for (e.g. in the case of significant merge conflicts) At any given time, the OnDocs label will properly describe what’s running on Docs / CI. The base for this build is 9.0.x branch, currently. Of course, we highly encourage you to pull in changes merged into master into your local release/test repositories, and do a similar test in your test and production environments. I think the processes that we have in place now on Github + CI + Docs is a pretty solid workflow, but I’m also open for suggestions for improvements. Thanks, — leif https://github.com/apache/trafficserver/pulls?utf8=✓&q=is%3Apr+label%3AOnDocs+
