I have the same comments as the 3.5.5 release. Binary contains incorrect symlinks and we probably need to add binaries for other language clients for release validation here.
-- Divij Vaidya On Tue, Jan 24, 2023 at 2:42 AM David Bechberger <d...@bechberger.com> wrote: > Looks good to me > > VOTE +1 (non-binding) > > On Mon, Jan 23, 2023 at 10:29 AM Ken Hu <k...@bitquilltech.com.invalid> > wrote: > > > Thanks Yang. This looks good to me. > > > > VOTE +1 (non-binding) > > > > On Mon, Jan 23, 2023 at 10:05 AM Cole Greer > > <cole.gr...@improving.com.invalid> wrote: > > > > > Thanks for putting this all together Yang. I’ve dug through the docs > and > > > artifacts and it all looks good to me. > > > > > > VOTE +1 (non-binding) > > > > > > Regards, > > > > > > Cole Greer > > > > > > > > > From: Valentyn Kahamlyk <valent...@bitquilltech.com.INVALID> > > > Date: Monday, January 23, 2023 at 9:16 AM > > > To: dev@tinkerpop.apache.org <dev@tinkerpop.apache.org> > > > Subject: Re: [VOTE] TinkerPop 3.6.2 Release > > > Yang, thank you for preparing the release! > > > > > > VOTE +1 (non-binding) > > > > > > On Mon, Jan 23, 2023 at 8:16 AM Florian Hockmann < > f...@florian-hockmann.de > > > > > > wrote: > > > > > > > I had the same problem with bin/validate-distribution.sh as in the > > other > > > > thread, but again, this shouldn't be a problem for the release > > process. I > > > > again skimmed over the docs and everything looks good to me. > > > > > > > > VOTE +1 > > > > > > > > -----Ursprüngliche Nachricht----- > > > > Von: Yang Xia <ya...@bitquilltech.com.INVALID> > > > > Gesendet: Samstag, 21. Januar 2023 06:27 > > > > An: dev@tinkerpop.apache.org > > > > Betreff: [VOTE] TinkerPop 3.6.2 Release > > > > > > > > Hello, > > > > > > > > We are happy to announce that TinkerPop 3.6.2 is ready for release. > > > > > > > > The release artifacts can be found at this location: > > > > https://dist.apache.org/repos/dist/dev/tinkerpop/3.6.2/ > > > > > > > > The source distribution is provided by: > > > > apache-tinkerpop-3.6.2-src.zip > > > > > > > > Two binary distributions are provided for user convenience: > > > > apache-tinkerpop-gremlin-console-3.6.2-bin.zip > > > > apache-tinkerpop-gremlin-server-3.6.2-bin.zip > > > > > > > > The GPG key used to sign the release artifacts is available at: > > > > https://dist.apache.org/repos/dist/dev/tinkerpop/KEYS > > > > > > > > The online docs can be found here: > > > > https://tinkerpop.apache.org/docs/3.6.2/ (user docs) > > > > https://tinkerpop.apache.org/docs/3.6.2/upgrade/ (upgrade > > docs) > > > > https://tinkerpop.apache.org/javadocs/3.6.2/core/ (core > > javadoc) > > > > https://tinkerpop.apache.org/javadocs/3.6.2/full/ (full > > javadoc) > > > > https://tinkerpop.apache.org/dotnetdocs/3.6.2/ (.NET API > docs) > > > > https://tinkerpop.apache.org/jsdocs/3.6.2/ (Javascript API > > docs) > > > > > > > > The Git tag can be found here: > > > > https://github.com/apache/tinkerpop/tree/3.6.2 > > > > > > > > The release notes are available here: > > > > > > > https://github.com/apache/tinkerpop/blob/3.6.2/CHANGELOG.asciidoc > > > > > > > > Please note that you may get "rm: cannot remove" permission errors > when > > > > running bin/validate-distribution.sh, which we have made a note to > fix > > > > after the release. The temporary solution is to run this script with > > sudo > > > > or editing the script to add sudo to "rm" commands. > > > > > > > > The [VOTE] will be open for the next 72 hours --- closing Monday > > (January > > > > 23, 2023) at 9:30pm PST (UTC−08:00). > > > > > > > > My vote is +1. > > > > > > > > Thank you very much, > > > > > > > > Yang Xia > > > > *--* > > > > *Yang Xia* > > > > Software Engineer > > > > Bit Quill Technologies Inc. > > > > ya...@bitquilltech.com > > > > https://www.bitquill.com > > > > > > > > This email message is for the sole use of the intended recipient(s) > and > > > > may contain confidential and privileged information. Any > unauthorized > > > > review, use, disclosure, or distribution is prohibited. If you are > not > > > the > > > > intended recipient, please contact the sender by reply email and > > destroy > > > > all copies of the original message. Thank you. > > > > > > > > > > > > > >
