Hi all,

The vote to adopt the release branch naming and release cadence policy
<https://lists.apache.org/thread/5cphypqlzgyrc5s5bqyj1q0p7lvpxms0> has
passed. The vote was open for more than 72 hours.

Vote result:

+1:
* Yicong Huang
* Chen Li
  Ryan Zhang
* Jiadong Bai

0:
  Kun Woo Park

-1:
  None

* denotes a binding vote.

With this result, we will adopt the following release policy:

1. Use release branches for maintenance lines. A release branch represents
a release line, such as the v1.1.x line or the v1.2.x line.
2. Use tags for exact releases. A tag represents the exact commit on a
release line used for a specific release.
3. Use patch releases only for safe fixes to an existing release line.
4. Use minor releases for normal releases from main.
5. Aim for one minor release every three months.

We will execute the steps:
- Rename release/v1.1.0-incubating to release/v1.1.
- Make sure v1.1.0-incubating exists as a tag on the approved release
commit.
- Cut release/v1.2 from main.
- Prepare v1.2.0-incubating release candidates from release/v1.2.
- After approval, tag the approved release commit as v1.2.0-incubating.
- Use release/v1.2 for possible future v1.2.x patch releases.
- After v1.2.0-incubating, wait about three months before cutting
release/v1.3.

Thanks everyone for the discussion and votes.

Best regards,
Yicong Huang

Reply via email to