Hi, Since we have an additional branch (quic-latest) for HTTP/3 and QUIC, there was a confusion about what branch you should make a PR for. So I'd like to propose a guideline for HTTP/3 or QUIC related PRs below.
- Make a PR for quic-latest if the change adds new features - Make a PR for quic-latest if the change is drastic - Make a PR for master if the change fixes / improves draft-27 support on master and 9.0.x - Make a PR for quic-latest if none of these applies There is no change actually. We maintain master and release branches as the same manner as before. Since the code is already on master, we should maintain it. quic-latest branch is to allow rapid changes for catching up draft updates and interop. In case you are unsure, quic-latest is a safe bet. I'd make (or request you to make) another PR for master after landing your PR if necessary. In fact, I sometimes fix bugs on quic-latest first and then make PRs for master. Also, I'm going to check all PRs that have QUIC or HTTP/3 labels, but it doesn't mean you should wait for an approval from me. I may just leave it if the change isn't really related to QUIC or HTTP/3 (e.g. typo, coding style, etc). Thanks, Masakazu
