Re: [DISCUSS] gremlinpython 3.2.7rc1 and 3.3.1rc1

[David Brown]

Thanks Stephen!

On Tue, Oct 31, 2017 at 9:28 AM, Stephen Mallette  wrote:
> I just published the two release candidates for gremlin-python.
>
> On Wed, Oct 25, 2017 at 4:41 PM, David Brown  wrote:
>
>> +1 definitely helps me out
>>
>> On Wed, Oct 25, 2017 at 1:12 PM, Stephen Mallette 
>> wrote:
>> > I'd like to propose that we do release candidates of gremlinpython from
>> > both master and tp32. We're not quite ready for a full official release
>> as
>> > of yet (personally, I'd like to see .NET ready to go before we do that),
>> > but we did just fix some bugs in gremlinpython around serialization and
>> > dependencies that would be helpful to developers working on the bleeding
>> > edge of things if we had a release candidate out there.
>> >
>> > If there are no objections in the next 72 hours (Saturday October 28th,
>> > 2017, 4pm EST) I'll assume lazy consensus and proceed with deploying:
>> > 3.2.7rc1 and 3.3.1rc1
>> >
>> > Thanks,
>> >
>> > Stephen
>>
>>
>>
>> --
>> David M. Brown
>> R.A. CulturePlex Lab, Western University
>>



-- 
David M. Brown
R.A. CulturePlex Lab, Western University

Re: [DISCUSS] gremlinpython 3.2.7rc1 and 3.3.1rc1

[Stephen Mallette]

I just published the two release candidates for gremlin-python.

On Wed, Oct 25, 2017 at 4:41 PM, David Brown  wrote:

> +1 definitely helps me out
>
> On Wed, Oct 25, 2017 at 1:12 PM, Stephen Mallette 
> wrote:
> > I'd like to propose that we do release candidates of gremlinpython from
> > both master and tp32. We're not quite ready for a full official release
> as
> > of yet (personally, I'd like to see .NET ready to go before we do that),
> > but we did just fix some bugs in gremlinpython around serialization and
> > dependencies that would be helpful to developers working on the bleeding
> > edge of things if we had a release candidate out there.
> >
> > If there are no objections in the next 72 hours (Saturday October 28th,
> > 2017, 4pm EST) I'll assume lazy consensus and proceed with deploying:
> > 3.2.7rc1 and 3.3.1rc1
> >
> > Thanks,
> >
> > Stephen
>
>
>
> --
> David M. Brown
> R.A. CulturePlex Lab, Western University
>

Re: [DISCUSS] gremlinpython 3.2.7rc1 and 3.3.1rc1

[David Brown]

+1 definitely helps me out

On Wed, Oct 25, 2017 at 1:12 PM, Stephen Mallette  wrote:
> I'd like to propose that we do release candidates of gremlinpython from
> both master and tp32. We're not quite ready for a full official release as
> of yet (personally, I'd like to see .NET ready to go before we do that),
> but we did just fix some bugs in gremlinpython around serialization and
> dependencies that would be helpful to developers working on the bleeding
> edge of things if we had a release candidate out there.
>
> If there are no objections in the next 72 hours (Saturday October 28th,
> 2017, 4pm EST) I'll assume lazy consensus and proceed with deploying:
> 3.2.7rc1 and 3.3.1rc1
>
> Thanks,
>
> Stephen



-- 
David M. Brown
R.A. CulturePlex Lab, Western University

[DISCUSS] gremlinpython 3.2.7rc1 and 3.3.1rc1

[Stephen Mallette]

I'd like to propose that we do release candidates of gremlinpython from
both master and tp32. We're not quite ready for a full official release as
of yet (personally, I'd like to see .NET ready to go before we do that),
but we did just fix some bugs in gremlinpython around serialization and
dependencies that would be helpful to developers working on the bleeding
edge of things if we had a release candidate out there.

If there are no objections in the next 72 hours (Saturday October 28th,
2017, 4pm EST) I'll assume lazy consensus and proceed with deploying:
3.2.7rc1 and 3.3.1rc1

Thanks,

Stephen