Maybe we need to add DISCLAIMER in binary release too, and do not publish tpcds module both in source or binary
On 2021/08/22 00:29:42, Cheng Pan <[email protected]> wrote: > Hello Apache Kyuubi PPMC and Community, > > Please vote on releasing the following candidate as > Apache Kyuubi (Incubating) version v1.3.0-incubating. > > The VOTE will remain open for at least 72 hours. > > [ ] +1 Release this package as Apache Kyuubi v1.3.0-incubating > [ ] +0 > [ ] -1 Do not release this package because ... > > To learn more about Apache Kyuubi (Incubating), please see > https://kyuubi.apache.org/ > > The tag to be voted on is v1.3.0-incubating-rc1 (commit 8cd2850): > https://github.com/apache/incubator-kyuubi/tree/v1.3.0-incubating-rc1 > > The release files, including signatures, digests, etc. can be found at: > https://dist.apache.org/repos/dist/dev/incubator/kyuubi/v1.3.0-incubating-rc1/ > > Signatures used for Kyuubi RCs can be found in this file: > https://dist.apache.org/repos/dist/dev/incubator/kyuubi/KEYS > (Signed by ED4E2E5B) > > The staging repository for this release can be found at: > https://repository.apache.org/content/repositories/orgapachekyuubi-1001/ > > The commit list since the last RC: > https://github.com/apache/incubator-kyuubi/compare/v1.3.0-incubating-rc0...v1.3.0-incubating-rc1 > > FAQ > > ================================= > How can I help test this release? > ================================= > > If you are a Kyuubi user, you can help us test this release by taking > an existing Kyuubi workload and running on this release candidate, then > reporting any regressions. > > In the Java/Scala, you can add the staging repository to your projects > resolvers > and test with the RC (make sure to clean up the artifact cache before/after > so > you don't end up building with a out of date RC going forward). > > ============================================================== > What should happen to GitHub issues still targeting v1.3.0-incubating? > ============================================================== > > Committers should look at those and triage. Extremely important bug fixes, > documentation, and API tweaks that impact compatibility should be worked on > immediately. Everything else please retarget to an appropriate release. > > ======================= > But my bug isn't fixed? > ======================= > > In order to make timely releases, we will typically not hold the release > unless > the bug in question is a regression from the previous release. That being > said, > if there is something which is a regression that has not been correctly > targeted > please ping me or a committer to help target the issue. >
