OK that one is merged.

On Wed, Feb 3, 2021 at 8:57 AM Yuxuan Wang <yuxuan.w...@reddit.com> wrote:

> Thanks, Jens! I want to include https://github.com/apache/thrift/pull/2307
> (THRIFT-5337) as well, I'm just waiting for travis to pass.
>
> Also does anyone know if we have any known issues with travis? the travis
> runs for that PR always failed with a very long delay then not running
> anything, I'm not sure if it's the author's way of creating the PR is weird
> and triggered some corner case of travis, or is travis just not working in
> general. I'll create another PR with the same code to try to get travis
> running.
>
> On Wed, Feb 3, 2021 at 12:48 AM Jens Geyer <jensge...@hotmail.com> wrote:
>
>> Hi all,
>>
>> Unless there are no objections from anyone I am going to create the
>> 0.14.0
>> branch tomorrow, based on whatever is on master at that time.
>>
>> Since nobody seems interested enough in reviewing/fixing this minorish
>> issue, THRIFT-5344 will not be included.
>>
>> Have fun,
>> JensG
>>
>>
>>
>> -----Ursprüngliche Nachricht-----
>> From: Jens Geyer
>> Sent: Tuesday, January 19, 2021 8:53 AM
>> To: dev@thrift.apache.org
>> Subject: Re: Plans/process for 0.14.0 release?
>>
>> Hi,
>>
>> > Can reviewed them and I merged them today
>>
>> So technically we are where we want to be? That's good news indeed.
>>
>> > Please give me a few more days,
>>
>> Much appreciated, looking forward to it.
>>
>> Thanks for all the work,
>> JensG
>>
>>
>> -----Ursprüngliche Nachricht-----
>> From: Yuxuan Wang
>> Sent: Monday, January 18, 2021 5:32 AM
>> To: dev@thrift.apache.org
>> Subject: Re: Plans/process for 0.14.0 release?
>>
>> Can reviewed them and I merged them today. Please give me a few more days,
>> I'll deploy our production system to the newest master version on Tuesday,
>> and run it for a few days to make sure that there's no bugs and such.
>>
>> On Wed, Jan 6, 2021 at 1:00 PM Jens Geyer <jensge...@hotmail.com> wrote:
>>
>> >
>> > Cool! Can you throw some info mail when all is ready? I'll cut the
>> branch
>> > then and see how far I can get it done.
>> >
>> >
>> > -----Ursprüngliche Nachricht-----
>> > From: Duru Can Celasun
>> > Sent: Tuesday, January 5, 2021 11:46 PM
>> > To: dev@thrift.apache.org
>> > Subject: Re: Plans/process for 0.14.0 release?
>> >
>> > I have those PRs on my backlog, sorry for the delay :) I'll definitely
>> > take
>> > a look this week.
>> >
>> > On Tue, 5 Jan 2021, at 22:40, Yuxuan Wang wrote:
>> > > For Go I certainly want to merge
>> > > https://github.com/apache/thrift/pull/2298
>> > > & https://github.com/apache/thrift/pull/2296 before the next release
>> > > (v0.14.0). @Can might take a look at them? :)
>> > >
>> > > On Tue, Jan 5, 2021 at 2:38 PM Duru Can Celasun <dcela...@apache.org>
>> > > wrote:
>> > >
>> > > > I'm in favour of cutting a new release, though I never did one for
>> > > > thrift
>> > > > and I won't have the time to get involved any time soon.
>> > > >
>> > > > On Tue, 5 Jan 2021, at 21:47, Jens Geyer wrote:
>> > > > > @all
>> > > > >
>> > > > > > Good question. I'm in favour of it. Who does it?
>> > > > >
>> > > > > That was actually a real question. I support the proposal but
>> would
>> > > > > like
>> > > > to
>> > > > > know the opinion of other people.
>> > > > > - Anything we absolutely should include in the next release (i.e.
>> > > > blockers)?
>> > > > > - Or is everybody happy already and thinks we are ready to cut a
>> > > > > branch
>> > > > and
>> > > > > do the real heavy lifting?
>> > > > >
>> > > > > That's not a real vote, but at least some feedback would be
>> helpful.
>> > > > >
>> > > > > Have fun,
>> > > > > JensG
>> > > > >
>> > > > >
>> > > > > -----Ursprüngliche Nachricht-----
>> > > > > From: Yuxuan Wang
>> > > > > Sent: Monday, January 4, 2021 9:41 PM
>> > > > > To: dev@thrift.apache.org
>> > > > > Subject: Plans/process for 0.14.0 release?
>> > > > >
>> > > > > Judging from history the end of the years are usually when we do
>> > > > releases,
>> > > > > is there a plan for 0.14.0 release?
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>> >
>>
>>

Reply via email to