Re: code freeze 3.2.10/3.3.4

2018-10-29 Thread Stephen Mallette
tp32 is now open for business - snapshots/docs are deployed. On Fri, Oct 26, 2018 at 8:18 AM Stephen Mallette wrote: > I'm +0 on formalizing too muchsome common sense like "release next > cycle unless someone can provide a proof of concept or just feels strongly > otherwise" is fine by me. >

Re: code freeze 3.2.10/3.3.4

2018-10-26 Thread Stephen Mallette
I'm +0 on formalizing too muchsome common sense like "release next cycle unless someone can provide a proof of concept or just feels strongly otherwise" is fine by me. > If you're going to reopen tp32, then I'll retarget sounds good - thanks for staying up on the "security" stuff On Fri, Oct

Re: code freeze 3.2.10/3.3.4

2018-10-26 Thread Robert Dale
If you're going to reopen tp32, then I'll retarget https://github.com/apache/tinkerpop/pull/969 Robert Dale On Fri, Oct 26, 2018 at 7:56 AM Robert Dale wrote: > So to answer your earlier question on security fixes, the driver should be > our security policy ;-) > > For example, if tp32 is not

Re: code freeze 3.2.10/3.3.4

2018-10-26 Thread Robert Dale
So to answer your earlier question on security fixes, the driver should be our security policy ;-) For example, if tp32 is not officially closed and accepts bug fixes, and given "security problems are just bugs" [1], then tp32 should get security-related bug fixes. We can use CVSS [2] to score vu

Re: code freeze 3.2.10/3.3.4

2018-10-26 Thread Stephen Mallette
tp32... i started thinking that we could keep a JIRA ticket open that had a list of bugs we might backport to tp32 should we have some triggering event, buti dunno. maybe we go with a first step at this and re-open the branch but just ship security+bug fixes at it and not try to wa

Re: code freeze 3.2.10/3.3.4

2018-10-22 Thread Stephen Mallette
there's always going to be those kinds of things though right? can we get away with doing stuff to tp32 only when there is some specific demand for a 3.2.11. like, that fix on its own doesn't feel like something we'd trigger a release overor would we? On Sat, Oct 20, 2018 at 9:27 AM Robert Dal

Re: code freeze 3.2.10/3.3.4

2018-10-20 Thread Robert Dale
You don't want to put https://issues.apache.org/jira/browse/TINKERPOP-2068 on tp32? Robert Dale On Fri, Oct 19, 2018 at 6:03 PM Stephen Mallette wrote: > > I created a ticket to track this and I can probably take care of it next > week > > that makes sense, thank you. > > separately, code fre

Re: code freeze 3.2.10/3.3.4

2018-10-19 Thread Stephen Mallette
> I created a ticket to track this and I can probably take care of it next week that makes sense, thank you. separately, code freeze is now lifted on tp33 - i've bumped to 3.3.5-SNAPSHOT, published initial docs/artifacts and all is good to go. I've left tp32 on 3.2.10 until we decide to actually

Re: code freeze 3.2.10/3.3.4

2018-10-19 Thread Florian Hockmann
We currently use this to push the package: ${nugetExe} push Gremlin.Net/bin/Gremlin.Net.*.nupkg which pushes all NuGet packages starting with Gremlin.Net. You probably also had the package for version 3.4.0-rc2 in that directory. So, nuget.exe tried to push that version again which isn't allowed

Re: code freeze 3.2.10/3.3.4

2018-10-19 Thread Stephen Mallette
Florian, any idea what's going on with this error when i deployed 3.3.4: main: [echo] nuget.exe already downloaded. [exec] Pushing Gremlin.Net.3.3.4.nupkg to ' https://www.nuget.org/api/v2/package'... [exec] PUT https://www.nuget.org/api/v2/package/ [exec] Created https://w

Re: code freeze 3.2.10/3.3.4

2018-10-12 Thread Stephen Mallette
Robert Dale is without power so I pushed the 3.2.10-SNAPSHOT artifacts and docs too: http://tinkerpop.apache.org/docs/3.2.10-SNAPSHOT/ On Fri, Oct 12, 2018 at 8:22 AM Stephen Mallette wrote: > I just published final 3.3.4-SNAPSHOT artifacts and docs: > > http://tinkerpop.apache.org/docs/3.3.4

Re: code freeze 3.2.10/3.3.4

2018-10-12 Thread Stephen Mallette
I just published final 3.3.4-SNAPSHOT artifacts and docs: http://tinkerpop.apache.org/docs/3.3.4-SNAPSHOT/ On Sun, Oct 7, 2018 at 8:33 AM Robert Dale wrote: > I'll take 3.2.10. > > Robert Dale > > > On Fri, Oct 5, 2018 at 7:40 PM Stephen Mallette > wrote: > > > So - code freeze for the tp32 an

Re: code freeze 3.2.10/3.3.4

2018-10-07 Thread Robert Dale
I'll take 3.2.10. Robert Dale On Fri, Oct 5, 2018 at 7:40 PM Stephen Mallette wrote: > So - code freeze for the tp32 and tp33 branches is in effect at this point. > We'll use this thread to discuss issues related to 3.2.10 and 3.3.4 leading > up to the build of release artifacts for 10/15. We

code freeze 3.2.10/3.3.4

2018-10-05 Thread Stephen Mallette
So - code freeze for the tp32 and tp33 branches is in effect at this point. We'll use this thread to discuss issues related to 3.2.10 and 3.3.4 leading up to the build of release artifacts for 10/15. We currently have a few PRs that need merging to those branches, https://github.com/apache/tinkerp