Hi, Navina,
Great! Thanks!
-Yi
On Sun, Aug 7, 2016 at 8:01 PM, Navina Ramesh
wrote:
> Thanks , Yi! I was just about to send the email.
>
> +1 (Binding) = 3
> +1 (non-binding) = 5
>
> I think this is good enough. I will publish the release by tomorrow.
>
> Thanks!
> Navina
>
>
> On Sun, Aug 7,
Thanks , Yi! I was just about to send the email.
+1 (Binding) = 3
+1 (non-binding) = 5
I think this is good enough. I will publish the release by tomorrow.
Thanks!
Navina
On Sun, Aug 7, 2016 at 7:53 PM, Yi Pan wrote:
> It has been more than 5 days and we have got 3 +1 (binding) and 5 +1
> (n
It has been more than 5 days and we have got 3 +1 (binding) and 5 +1
(non-binding) already. Can we conclude this vote? Thanks!
On Tue, Aug 2, 2016 at 1:10 PM, Boris Shkolnik wrote:
> +1 (non-binding).
>
> Boris.
>
> On Mon, Aug 1, 2016 at 11:39 AM, Navina Ramesh
> > wrote:
>
> > Hey all,
> >
>
+1 (non-binding).
Boris.
On Mon, Aug 1, 2016 at 11:39 AM, Navina Ramesh wrote:
> Hey all,
>
> This is a call for a vote on a release of Apache Samza 0.10.0. Thanks
> to everyone
> who has contributed to this release. We are very glad to see some new
> contributors in this release.
>
> **NOTE**:
> On Aug 1, 2016, at 5:24 PM, Navina Ramesh
> wrote:
>
> Are you referring to the Gemfile.lock in docs/ ? I do see that in the
> source release.
I was mistaken. Apparently it is OK to check in Gemfile.lock; see
http://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/
estion - the key used to sign isn't in the KEYS file in the git
> > repo
> > > -- is this a convenieence mechanism or does the release process mean
> it
> > > should be there?
> > >
> > > Garry
> > >
> > > -Original Message-
t; > -Original Message-
> > From: Jacob Maes [mailto:jacob.m...@gmail.com]
> > Sent: Monday, August 01, 2016 7:45 PM
> > To: dev@samza.apache.org
> > Subject: Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
> >
> > +1 non-binding
> > Lots of good fix
>> should be there?
>>
>> Garry
>>
>> -Original Message-----
>> From: Jacob Maes [mailto:jacob.m...@gmail.com]
>> Sent: Monday, August 01, 2016 7:45 PM
>> To: dev@samza.apache.org
>> Subject: Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
>&g
@samza.apache.org
Subject: Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
@Garry: Yeah. I wasn't very clear about it either.
@Yi: Do you know if it is a part of the release process to add my keys to the
KEYS file in git repo?
Navina
On Mon, Aug 1, 2016 at 12:47 PM, Garry Turkington <
g
gt; -Original Message-
> From: Jacob Maes [mailto:jacob.m...@gmail.com]
> Sent: Monday, August 01, 2016 7:45 PM
> To: dev@samza.apache.org
> Subject: Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
>
> +1 non-binding
> Lots of good fixes in this release.
>
> On Mon, Aug
From: Jacob Maes [mailto:jacob.m...@gmail.com]
Sent: Monday, August 01, 2016 7:45 PM
To: dev@samza.apache.org
Subject: Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
+1 non-binding
Lots of good fixes in this release.
On Mon, Aug 1, 2016 at 11:41 AM, Jagadish Venkatraman < jagadish1...@gmail.com
+1 non-binding
Lots of good fixes in this release.
On Mon, Aug 1, 2016 at 11:41 AM, Jagadish Venkatraman <
jagadish1...@gmail.com> wrote:
> Thanks for driving this release.+1 approve (non-binding)
>
> Thanks,
> Jagadish
>
> On Mon, Aug 1, 2016 at 11:39 AM, Navina Ramesh
> > wrote:
>
> > Hey all,
+1 (non-binding).
Thanks,
Xinyu
On Mon, Aug 1, 2016 at 11:41 AM, Jagadish Venkatraman <
jagadish1...@gmail.com> wrote:
> Thanks for driving this release.+1 approve (non-binding)
>
> Thanks,
> Jagadish
>
> On Mon, Aug 1, 2016 at 11:39 AM, Navina Ramesh
> > wrote:
>
> > Hey all,
> >
> > This is a
Thanks for driving this release.+1 approve (non-binding)
Thanks,
Jagadish
On Mon, Aug 1, 2016 at 11:39 AM, Navina Ramesh wrote:
> Hey all,
>
> This is a call for a vote on a release of Apache Samza 0.10.0. Thanks
> to everyone
> who has contributed to this release. We are very glad to see some
Hey all,
This is a call for a vote on a release of Apache Samza 0.10.0. Thanks
to everyone
who has contributed to this release. We are very glad to see some new
contributors in this release.
**NOTE**: This release is primarily a bug-fix release with no major changes
to the public api. Since we ar
15 matches
Mail list logo
