VOTE +1

Cheers,
Kelvin 

> On Jan 13, 2022, at 4:08 AM, Florian Hockmann <f...@florian-hockmann.de> 
> wrote:
> 
> Thanks for fixing it. Everything looks good now.
> 
> VOTE +1
> 
> -----Ursprüngliche Nachricht-----
> Von: Stephen Mallette <spmalle...@gmail.com> 
> Gesendet: Mittwoch, 12. Januar 2022 16:38
> An: dev@tinkerpop.apache.org
> Betreff: Re: [VOTE] TinkerPop 3.4.13 Release
> 
> The problem with .NET docs was related to mono as you suggested on the
> 3.5.2 thread - it's fixed now for 3.4.13.
> 
>> On Wed, Jan 12, 2022 at 4:13 AM Florian Hockmann <f...@florian-hockmann.de>
>> wrote:
>> 
>> I just checked the links, and the .NET docs seem to be missing. I'm at 
>> least getting a 404.
>> 
>> Apart from that, everything looks good to me. I also downloaded the 
>> binary distributions and performed a quick smoke test with Gremlin 
>> Console and Gremlin Server.
>> 
>> -----Ursprüngliche Nachricht-----
>> Von: Stephen Mallette <spmalle...@gmail.com>
>> Gesendet: Dienstag, 11. Januar 2022 13:20
>> An: dev@tinkerpop.apache.org
>> Betreff: Re: [VOTE] TinkerPop 3.4.13 Release
>> 
>> tldr; failing GH Actions for 3.4-dev and the 3.4.13 tag can be 
>> ignored, i think it's fine.
>> 
>> another side note about this release - it's not pretty but if you look 
>> at GH Actions it will show 3.4-dev currently failing the build in a 
>> lot of ways. i think that is due to the nature of how the build is 
>> being executed in there where it tries to save some time by skipping 
>> the build of some modules. Specifically, it skips building GLVs in 
>> cases where they aren't necessary, like for spark-gremlin, but i guess 
>> our code coverage module gremlin-coverage is still looking for 
>> gremlin-python which still had jython/jvm bindings on 3.4-dev and is 
>> causing failures because 3.4.13 technically doesn't exist yet. I'd 
>> imagine that once it releases I could re-run that job to success to pretty 
>> it up as the last release on that line.
>> 
>> In any case if it was really a problem then the smoke tests would have 
>> failed as well as the full build. Also, 3.5.-dev/3.5.2 had no such 
>> problems with the same build configuration because gremlin-python had 
>> it's jvm bindings removed and it is a pure python project now.
>> 
>> On Mon, Jan 10, 2022 at 1:21 PM Stephen Mallette 
>> <spmalle...@gmail.com>
>> wrote:
>> 
>>> .......and what January release would be complete without flubbing 
>>> the year in the changelog and upgrade docs? will fix that manually 
>>> on the website and in git.
>>> 
>>> On Mon, Jan 10, 2022 at 1:16 PM Stephen Mallette 
>>> <spmalle...@gmail.com>
>>> wrote:
>>> 
>>>> Hello,
>>>> 
>>>> We are happy to announce that TinkerPop 3.4.13 is ready for release.
>>>> 
>>>> The release artifacts can be found at this location:
>>>>        https://dist.apache.org/repos/dist/dev/tinkerpop/3.4.13/
>>>> 
>>>> The source distribution is provided by:
>>>>        apache-tinkerpop-3.4.13-src.zip
>>>> 
>>>> Two binary distributions are provided for user convenience:
>>>>        apache-tinkerpop-gremlin-console-3.4.13-bin.zip
>>>>        apache-tinkerpop-gremlin-server-3.4.13-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.4.13/ (user docs)
>>>>        https://tinkerpop.apache.org/docs/3.4.13/upgrade/ (upgrade
>> docs)
>>>>        https://tinkerpop.apache.org/javadocs/3.4.13/core/ (core
>> javadoc)
>>>>        https://tinkerpop.apache.org/javadocs/3.4.13/full/ (full
>> javadoc)
>>>>        https://tinkerpop.apache.org/dotnetdocs/3.4.13/ (.NET API docs)
>>>>        https://tinkerpop.apache.org/jsdocs/3.4.13/ (Javascript API
>>>> docs)
>>>> 
>>>> The tag in Apache Git can be found here:
>>>>        https://github.com/apache/tinkerpop/tree/3.4.13
>>>> 
>>>> The release notes are available here:
>>>> 
>>>> https://github.com/apache/tinkerpop/blob/3.4.13/CHANGELOG.asciidoc
>>>> 
>>>> The [VOTE] will be open for the next 72 hours --- closing 
>>>> Thursday(January 13, 2022) at 10:30am ET.
>>>> 
>>>> My vote is +1.
>>>> 
>>> 
>> 
>> 
> 

Reply via email to