Re: Subject: [VOTE] TinkerPop 3.5.4 Release

Thanks for the detailed explanation Stephen. I am glad that I have someone experienced like you guiding me as I learn the new responsibility of being a PMC member. I agree, we don’t need to block the release for the change log irregularities. But let’s do fix them as soon as possible after the rel

Re: Subject: [VOTE] TinkerPop 3.5.4 Release

I'll help Kelvin out with some answers here: > 1. I was looking at the commits going in the release and found that we are missing mention of certain changes in the changelog such as https://github.com/apache/tinkerpop/commit/e92d53fa0767fafa4e74f12ca84542d77d7d2976 , https://github.com/apache/tink

Re: [VOTE] TinkerPop 3.6.1 Release

I checked the links again and everything seemed good to me. So, assuming that Divij's comments are resolved: Vote +1 Von: Divij Vaidya Gesendet: Samstag, 23. Juli 2022 12:26 An: dev@tinkerpop.apache.org Betreff: Re: [VOTE] TinkerPop 3.6.1 Release Thanks again

Re: [VOTE] TinkerPop 3.6.1 Release

Thanks again Kelvin for picking up the responsibility for the release! I have similar questions with this release as I posted on the 3.5.4 vote thread such as some commits missing in changelog, Kelvin's public signature missing in GPG KEYS etc. I would wait for resolution on that thread before I r

Re: Subject: [VOTE] TinkerPop 3.5.4 Release

5. I found a broken link in the upgrade documentation. At https://tinkerpop.apache.org/docs/3.5.4/upgrade/#_gremlin_go, when we click on the "here" hyperlink on the line "For full documentation on the available API to give Gremlin Go a try, click here

Re: Subject: [VOTE] TinkerPop 3.5.4 Release

Fixing a typo -> "I am completely *not* sure about this but perhaps..." -- Divij Vaidya On Sat, Jul 23, 2022 at 12:04 PM Divij Vaidya wrote: > Hey Kelvin > > Thank you for picking up the responsibility for the release process. I > have a couple of questions before I can vote to go ahead with

Re: Subject: [VOTE] TinkerPop 3.5.4 Release

Hey Kelvin Thank you for picking up the responsibility for the release process. I have a couple of questions before I can vote to go ahead with the release. 1. I was looking at the commits going in the release and found that we are missing mention of certain changes in the changelog such as https