VOTE +1 (non-binding)

Thanks for getting this release out the door.

On Mon, Jan 23, 2023 at 10:29 AM Ken Hu <[email protected]>
wrote:

> Thanks Yang. This looks good to me.
>
> VOTE +1 (non-binding)
>
> On Mon, Jan 23, 2023 at 10:04 AM Cole Greer
> <[email protected]> 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 <[email protected]>
> > Date: Monday, January 23, 2023 at 9:19 AM
> > To: [email protected] <[email protected]>
> > Subject: Re: [VOTE] TinkerPop 3.5.5 Release
> > VOTE +1 (non-binding)
> >
> > On Fri, Jan 20, 2023 at 7:03 AM Florian Hockmann <[email protected]
> >
> > wrote:
> >
> > > Thanks a lot for taking care of the releases!
> > >
> > > I checked the links, skimmed over the docs and executed
> > > bin/validate-distribution.sh. This failed for me for some reason. It
> > > complains about a missing Docker image:
> > >
> > > failed to solve: tinkerpop/gremlin-server:3.5.5:
> > > docker.io/tinkerpop/gremlin-server:3.5.5: not found
> > >
> > > but that only happens during validation of the source distribution and
> is
> > > probably specific to my system and not related to this release. The
> other
> > > checks also already passed at that point. So, this shouldn't stop the
> > > release process.
> > >
> > > My vote is +1.
> > >
> > > -----Ursprüngliche Nachricht-----
> > > Von: Yang Xia <[email protected]>
> > > Gesendet: Donnerstag, 19. Januar 2023 23:13
> > > An: [email protected]
> > > Betreff: [VOTE] TinkerPop 3.5.5 Release
> > >
> > > Hello,
> > >
> > > We are happy to announce that TinkerPop 3.5.5 is ready for release.
> > >
> > > The release artifacts can be found at this location:
> > >         https://dist.apache.org/repos/dist/dev/tinkerpop/3.5.5/
> > >
> > > The source distribution is provided by:
> > >         apache-tinkerpop-3.5.5-src.zip
> > >
> > > Two binary distributions are provided for user convenience:
> > >         apache-tinkerpop-gremlin-console-3.5.5-bin.zip
> > >         apache-tinkerpop-gremlin-server-3.5.5-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.5.5/ (user docs)
> > >         https://tinkerpop.apache.org/docs/3.5.5/upgrade/ (upgrade
> docs)
> > >         https://tinkerpop.apache.org/javadocs/3.5.5/core/ (core
> javadoc)
> > >         https://tinkerpop.apache.org/javadocs/3.5.5/full/ (full
> javadoc)
> > >         https://tinkerpop.apache.org/dotnetdocs/3.5.5/ (.NET API docs)
> > >         https://tinkerpop.apache.org/jsdocs/3.5.5/ (Javascript API
> docs)
> > >
> > > The Git tag can be found here:
> > >         https://github.com/apache/tinkerpop/tree/3.5.5
> > >
> > > The release notes are available here:
> > >
> > https://github.com/apache/tinkerpop/blob/3.5.5/CHANGELOG.asciidoc
> > >
> > > Please note that when you run bin/validate-distribution.sh, you might
> get
> > > "rm: cannot remove" permission errors for some GLV test outputs. As
> this
> > > does not affect server/console nor the regular "mvn clean install"
> > > commands, we will not hold the release on that, but 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 Sunday
> (January
> > > 22, 2023) at 2:15pm, PST (UTC−08:00).
> > >
> > > My vote is +1.
> > >
> > > Thank you very much,
> > >
> > > Yang Xia
> > >
> > > *--*
> > > *Yang Xia*
> > > Software Engineer
> > > Bit Quill Technologies Inc.
> > > [email protected]
> > > 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.
> > >
> > >
> >
>

Reply via email to