+1 Thanks Cheng Pan drived the first release in the incubator. Also thank all contributors.
I verified the following things: - The signatures and digests for the release file - Unzip the bin file and check the LICENSE/NOTICE/DISCLAIMER files etc. - Build and run the UTs for v1.3.0-incubating-rc7 tag - Start a new Kyuubi Server (The release bin files can not work if you do not set SPARK_HOME and SPARK_CONF_DIR environments.) - Use Spark Beeline to connect the Kyuubi Server - Execute a sample sql: select timestamp '2021-09-01' - Check the server logs and Spark App UI BR, Wanqiang Ji On Mon, Aug 30, 2021 at 3:21 PM Cheng Pan <cheng...@apache.org> 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-rc7 (commit f1319e5): > https://github.com/apache/incubator-kyuubi/tree/v1.3.0-incubating-rc7 > > The release files, including signatures, digests, etc. can be found at: > https://dist.apache.org/repos/dist/dev/incubator/kyuubi/v1.3.0-incubating-rc7/ > > Signatures used for Kyuubi RCs can be found in this file: > https://dist.apache.org/repos/dist/dev/incubator/kyuubi/KEYS > > The staging repository for this release can be found at: > https://repository.apache.org/content/repositories/orgapachekyuubi-1007/ > > The commit list since the last RC: > https://github.com/apache/incubator-kyuubi/compare/v1.3.0-incubating-rc5...v1.3.0-incubating-rc7 > > 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. > Thanks, > Cheng Pan
