You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@samza.apache.org by Navina Ramesh <nr...@linkedin.com.INVALID> on 2016/08/01 18:39:28 UTC
[DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
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 are behind schedule in terms of releases, we
are combining the DISCUSS and VOTE email into a single VOTE email. If
anyone has objections, please do raise them. We plan to shortly follow-up
with a DISCUSS email for 0.11.0 release, that brings in new features in
multi-threading, REST api etc.
The release candidate can be downloaded from here:
http://home.apache.org/~navina/samza-0.10.1-rc0/
The release candidate is signed with pgp key 331C8F69, which can be found
on keyservers:
http://pgp.mit.edu/pks/lookup?op=get&search=0x331C8F69
The git tag is release-0.10.1-rc0 and signed with the same pgp key:
*https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1eb2dc1dbffc661f910b1272b233640
<https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1eb2dc1dbffc661f910b1272b233640>*
Test binaries have been published to Maven's staging repository, and
are available
here:
https://repository.apache.org/content/repositories/orgapachesamza-1012/
Note that the binaries were built with JDK7 without incident.
69 issues were resolved for this release:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND%20fixVersion%20in%20(0.10.1)%20AND%20status%20in%20(Resolved%2C%20Closed)
The vote will be open for 72 hours ( end in 12:00pm Thursday, 08/05/2016 ).
Please download the release candidate, check the hashes/signature, build it and
test it, and then please vote:
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)
+1 from my side for the release.
Cheers!
--
Navina R.
navina@apache.org
Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
Posted by Yi Pan <ni...@gmail.com>.
Hi, Navina,
Great! Thanks!
-Yi
On Sun, Aug 7, 2016 at 8:01 PM, Navina Ramesh <nr...@linkedin.com.invalid>
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, 2016 at 7:53 PM, Yi Pan <ni...@gmail.com> wrote:
>
> > 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 <bo...@gmail.com> wrote:
> >
> > > +1 (non-binding).
> > >
> > > Boris.
> > >
> > > On Mon, Aug 1, 2016 at 11:39 AM, Navina Ramesh
> > > <nramesh@linkedin.com.invalid
> > > > 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**: This release is primarily a bug-fix release with no major
> > > changes
> > > > to the public api. Since we are behind schedule in terms of releases,
> > we
> > > > are combining the DISCUSS and VOTE email into a single VOTE email. If
> > > > anyone has objections, please do raise them. We plan to shortly
> > follow-up
> > > > with a DISCUSS email for 0.11.0 release, that brings in new features
> in
> > > > multi-threading, REST api etc.
> > > >
> > > >
> > > > The release candidate can be downloaded from here:
> > > > http://home.apache.org/~navina/samza-0.10.1-rc0/
> > > >
> > > >
> > > > The release candidate is signed with pgp key 331C8F69, which can be
> > found
> > > > on keyservers:
> > > > http://pgp.mit.edu/pks/lookup?op=get&search=0x331C8F69
> > > >
> > > >
> > > > The git tag is release-0.10.1-rc0 and signed with the same pgp key:
> > > > *
> > > > https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=
> > > 33eff8a3e1eb2dc1dbffc661f910b1272b233640
> > > > <
> > > > https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=
> > > 33eff8a3e1eb2dc1dbffc661f910b1272b233640
> > > > >*
> > > >
> > > >
> > > > Test binaries have been published to Maven's staging repository, and
> > > > are available
> > > > here:
> > > > https://repository.apache.org/content/repositories/
> > orgapachesamza-1012/
> > > >
> > > >
> > > > Note that the binaries were built with JDK7 without incident.
> > > >
> > > > 69 issues were resolved for this release:
> > > >
> > > > https://issues.apache.org/jira/issues/?jql=project%20%
> > > 3D%20SAMZA%20AND%20fixVersion%20in%20(0.10.1)%20AND%
> > > 20status%20in%20(Resolved%2C%20Closed)
> > > >
> > > >
> > > > The vote will be open for 72 hours ( end in 12:00pm Thursday,
> > 08/05/2016
> > > ).
> > > >
> > > >
> > > > Please download the release candidate, check the hashes/signature,
> > build
> > > > it and
> > > > test it, and then please vote:
> > > >
> > > >
> > > > [ ] +1 approve
> > > >
> > > > [ ] +0 no opinion
> > > >
> > > > [ ] -1 disapprove (and reason why)
> > > >
> > > >
> > > > +1 from my side for the release.
> > > >
> > > > Cheers!
> > > > --
> > > > Navina R.
> > > > navina@apache.org
> > > >
> > >
> >
>
>
>
> --
> Navina R.
>
Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
Posted by Navina Ramesh <nr...@linkedin.com.INVALID>.
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 <ni...@gmail.com> wrote:
> 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 <bo...@gmail.com> wrote:
>
> > +1 (non-binding).
> >
> > Boris.
> >
> > On Mon, Aug 1, 2016 at 11:39 AM, Navina Ramesh
> > <nramesh@linkedin.com.invalid
> > > 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**: This release is primarily a bug-fix release with no major
> > changes
> > > to the public api. Since we are behind schedule in terms of releases,
> we
> > > are combining the DISCUSS and VOTE email into a single VOTE email. If
> > > anyone has objections, please do raise them. We plan to shortly
> follow-up
> > > with a DISCUSS email for 0.11.0 release, that brings in new features in
> > > multi-threading, REST api etc.
> > >
> > >
> > > The release candidate can be downloaded from here:
> > > http://home.apache.org/~navina/samza-0.10.1-rc0/
> > >
> > >
> > > The release candidate is signed with pgp key 331C8F69, which can be
> found
> > > on keyservers:
> > > http://pgp.mit.edu/pks/lookup?op=get&search=0x331C8F69
> > >
> > >
> > > The git tag is release-0.10.1-rc0 and signed with the same pgp key:
> > > *
> > > https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=
> > 33eff8a3e1eb2dc1dbffc661f910b1272b233640
> > > <
> > > https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=
> > 33eff8a3e1eb2dc1dbffc661f910b1272b233640
> > > >*
> > >
> > >
> > > Test binaries have been published to Maven's staging repository, and
> > > are available
> > > here:
> > > https://repository.apache.org/content/repositories/
> orgapachesamza-1012/
> > >
> > >
> > > Note that the binaries were built with JDK7 without incident.
> > >
> > > 69 issues were resolved for this release:
> > >
> > > https://issues.apache.org/jira/issues/?jql=project%20%
> > 3D%20SAMZA%20AND%20fixVersion%20in%20(0.10.1)%20AND%
> > 20status%20in%20(Resolved%2C%20Closed)
> > >
> > >
> > > The vote will be open for 72 hours ( end in 12:00pm Thursday,
> 08/05/2016
> > ).
> > >
> > >
> > > Please download the release candidate, check the hashes/signature,
> build
> > > it and
> > > test it, and then please vote:
> > >
> > >
> > > [ ] +1 approve
> > >
> > > [ ] +0 no opinion
> > >
> > > [ ] -1 disapprove (and reason why)
> > >
> > >
> > > +1 from my side for the release.
> > >
> > > Cheers!
> > > --
> > > Navina R.
> > > navina@apache.org
> > >
> >
>
--
Navina R.
Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
Posted by Yi Pan <ni...@gmail.com>.
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 <bo...@gmail.com> wrote:
> +1 (non-binding).
>
> Boris.
>
> On Mon, Aug 1, 2016 at 11:39 AM, Navina Ramesh
> <nramesh@linkedin.com.invalid
> > 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**: This release is primarily a bug-fix release with no major
> changes
> > to the public api. Since we are behind schedule in terms of releases, we
> > are combining the DISCUSS and VOTE email into a single VOTE email. If
> > anyone has objections, please do raise them. We plan to shortly follow-up
> > with a DISCUSS email for 0.11.0 release, that brings in new features in
> > multi-threading, REST api etc.
> >
> >
> > The release candidate can be downloaded from here:
> > http://home.apache.org/~navina/samza-0.10.1-rc0/
> >
> >
> > The release candidate is signed with pgp key 331C8F69, which can be found
> > on keyservers:
> > http://pgp.mit.edu/pks/lookup?op=get&search=0x331C8F69
> >
> >
> > The git tag is release-0.10.1-rc0 and signed with the same pgp key:
> > *
> > https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=
> 33eff8a3e1eb2dc1dbffc661f910b1272b233640
> > <
> > https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=
> 33eff8a3e1eb2dc1dbffc661f910b1272b233640
> > >*
> >
> >
> > Test binaries have been published to Maven's staging repository, and
> > are available
> > here:
> > https://repository.apache.org/content/repositories/orgapachesamza-1012/
> >
> >
> > Note that the binaries were built with JDK7 without incident.
> >
> > 69 issues were resolved for this release:
> >
> > https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20SAMZA%20AND%20fixVersion%20in%20(0.10.1)%20AND%
> 20status%20in%20(Resolved%2C%20Closed)
> >
> >
> > The vote will be open for 72 hours ( end in 12:00pm Thursday, 08/05/2016
> ).
> >
> >
> > Please download the release candidate, check the hashes/signature, build
> > it and
> > test it, and then please vote:
> >
> >
> > [ ] +1 approve
> >
> > [ ] +0 no opinion
> >
> > [ ] -1 disapprove (and reason why)
> >
> >
> > +1 from my side for the release.
> >
> > Cheers!
> > --
> > Navina R.
> > navina@apache.org
> >
>
Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
Posted by Boris Shkolnik <bo...@gmail.com>.
+1 (non-binding).
Boris.
On Mon, Aug 1, 2016 at 11:39 AM, Navina Ramesh <nramesh@linkedin.com.invalid
> 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**: This release is primarily a bug-fix release with no major changes
> to the public api. Since we are behind schedule in terms of releases, we
> are combining the DISCUSS and VOTE email into a single VOTE email. If
> anyone has objections, please do raise them. We plan to shortly follow-up
> with a DISCUSS email for 0.11.0 release, that brings in new features in
> multi-threading, REST api etc.
>
>
> The release candidate can be downloaded from here:
> http://home.apache.org/~navina/samza-0.10.1-rc0/
>
>
> The release candidate is signed with pgp key 331C8F69, which can be found
> on keyservers:
> http://pgp.mit.edu/pks/lookup?op=get&search=0x331C8F69
>
>
> The git tag is release-0.10.1-rc0 and signed with the same pgp key:
> *
> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1eb2dc1dbffc661f910b1272b233640
> <
> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1eb2dc1dbffc661f910b1272b233640
> >*
>
>
> Test binaries have been published to Maven's staging repository, and
> are available
> here:
> https://repository.apache.org/content/repositories/orgapachesamza-1012/
>
>
> Note that the binaries were built with JDK7 without incident.
>
> 69 issues were resolved for this release:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND%20fixVersion%20in%20(0.10.1)%20AND%20status%20in%20(Resolved%2C%20Closed)
>
>
> The vote will be open for 72 hours ( end in 12:00pm Thursday, 08/05/2016 ).
>
>
> Please download the release candidate, check the hashes/signature, build
> it and
> test it, and then please vote:
>
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove (and reason why)
>
>
> +1 from my side for the release.
>
> Cheers!
> --
> Navina R.
> navina@apache.org
>
RE: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
Posted by Garry Turkington <g....@improvedigital.com>.
This link seems to say the KEYS file needs be in the distribution directory on the Apache master site but not necessarily inside each released artifact. Which suggests the release process should ensure the signing key is in the publically accessible KEYS file. I guess its then a question of if we plan to version control that by keeping the master copy in the git root of master.
http://www.apache.org/dev/release-distribution.html#sigs-and-sums
Garry
-----Original Message-----
From: Navina Ramesh [mailto:nramesh@linkedin.com.INVALID]
Sent: Monday, August 01, 2016 9:05 PM
To: dev@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.turkington@improvedigital.com> wrote:
> +1 (binding)
>
> Built the source ran all tests and tried a sample test job. All looks good.
>
> One question - 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-----
> From: Jacob Maes [mailto:jacob.maes@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 <
> jagadish1989@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
> > <nramesh@linkedin.com.invalid
> > > 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**: This release is primarily a bug-fix release with no
> > > major
> > changes
> > > to the public api. Since we are behind schedule in terms of
> > > releases, we are combining the DISCUSS and VOTE email into a
> > > single VOTE email. If anyone has objections, please do raise them.
> > > We plan to shortly follow-up with a DISCUSS email for 0.11.0
> > > release, that brings in new features in multi-threading, REST api etc.
> > >
> > >
> > > The release candidate can be downloaded from here:
> > > http://home.apache.org/~navina/samza-0.10.1-rc0/
> > >
> > >
> > > The release candidate is signed with pgp key 331C8F69, which can
> > > be found on keyservers:
> > > http://pgp.mit.edu/pks/lookup?op=get&search=0x331C8F69
> > >
> > >
> > > The git tag is release-0.10.1-rc0 and signed with the same pgp key:
> > > *
> > >
> > https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3
> > e1
> > eb2dc1dbffc661f910b1272b233640
> > > <
> > >
> > https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3
> > e1
> > eb2dc1dbffc661f910b1272b233640
> > > >*
> > >
> > >
> > > Test binaries have been published to Maven's staging repository,
> > > and are available
> > > here:
> > > https://repository.apache.org/content/repositories/orgapachesamza-
> > > 10
> > > 12/
> > >
> > >
> > > Note that the binaries were built with JDK7 without incident.
> > >
> > > 69 issues were resolved for this release:
> > >
> > >
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20A
> > ND
> > %20fixVersion%20in%20(0.10.1)%20AND%20status%20in%20(Resolved%2C%20C
> > lo
> > sed)
> > >
> > >
> > > The vote will be open for 72 hours ( end in 12:00pm Thursday,
> > > 08/05/2016
> > ).
> > >
> > >
> > > Please download the release candidate, check the hashes/signature,
> > > build it and test it, and then please vote:
> > >
> > >
> > > [ ] +1 approve
> > >
> > > [ ] +0 no opinion
> > >
> > > [ ] -1 disapprove (and reason why)
> > >
> > >
> > > +1 from my side for the release.
> > >
> > > Cheers!
> > > --
> > > Navina R.
> > > navina@apache.org
> > >
> >
> >
> >
> > --
> > Jagadish V,
> > Graduate Student,
> > Department of Computer Science,
> > Stanford University
> >
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2016.0.7688 / Virus Database: 4627/12695 - Release Date:
> 07/27/16
>
--
Navina R.
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2016.0.7688 / Virus Database: 4627/12695 - Release Date: 07/27/16
Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
Posted by Julian Hyde <jh...@apache.org>.
> On Aug 1, 2016, at 5:24 PM, Navina Ramesh <nr...@linkedin.com.INVALID> 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/ <http://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/>.
Julian
Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
Posted by Navina Ramesh <nr...@linkedin.com.INVALID>.
Ok. I added my keys to the KEYS file.
@Julian: Thanks for the suggestion. I don't know the reason for choosing
home.apache.org as opposed to dist.apache.org. The latter does make more
sense. We will update the release procedure for 0.11.0.
Are you referring to the Gemfile.lock in docs/ ? I do see that in the
source release.
Navina
On Mon, Aug 1, 2016 at 3:55 PM, Yi Pan <ni...@gmail.com> wrote:
> Hi, Navina,
>
> Yes. You should put your key in the KEYS file.
>
> And +1 (binding) as I built and ran the zopkio integration test
> successfully as well.
>
> On Mon, Aug 1, 2016 at 1:05 PM, Navina Ramesh <nramesh@linkedin.com.invalid
> >
> wrote:
>
> > @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.turkington@improvedigital.com> wrote:
> >
> > > +1 (binding)
> > >
> > > Built the source ran all tests and tried a sample test job. All looks
> > good.
> > >
> > > One question - 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-----
> > > From: Jacob Maes [mailto:jacob.maes@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 <
> > > jagadish1989@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
> > > > <nramesh@linkedin.com.invalid
> > > > > 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**: This release is primarily a bug-fix release with no major
> > > > changes
> > > > > to the public api. Since we are behind schedule in terms of
> > > > > releases, we are combining the DISCUSS and VOTE email into a single
> > > > > VOTE email. If anyone has objections, please do raise them. We plan
> > > > > to shortly follow-up with a DISCUSS email for 0.11.0 release, that
> > > > > brings in new features in multi-threading, REST api etc.
> > > > >
> > > > >
> > > > > The release candidate can be downloaded from here:
> > > > > http://home.apache.org/~navina/samza-0.10.1-rc0/
> > > > >
> > > > >
> > > > > The release candidate is signed with pgp key 331C8F69, which can be
> > > > > found on keyservers:
> > > > > http://pgp.mit.edu/pks/lookup?op=get&search=0x331C8F69
> > > > >
> > > > >
> > > > > The git tag is release-0.10.1-rc0 and signed with the same pgp key:
> > > > > *
> > > > >
> > > >
> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1
> > > > eb2dc1dbffc661f910b1272b233640
> > > > > <
> > > > >
> > > >
> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1
> > > > eb2dc1dbffc661f910b1272b233640
> > > > > >*
> > > > >
> > > > >
> > > > > Test binaries have been published to Maven's staging repository,
> and
> > > > > are available
> > > > > here:
> > > > >
> https://repository.apache.org/content/repositories/orgapachesamza-10
> > > > > 12/
> > > > >
> > > > >
> > > > > Note that the binaries were built with JDK7 without incident.
> > > > >
> > > > > 69 issues were resolved for this release:
> > > > >
> > > > >
> > > >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND
> > > >
> %20fixVersion%20in%20(0.10.1)%20AND%20status%20in%20(Resolved%2C%20Clo
> > > > sed)
> > > > >
> > > > >
> > > > > The vote will be open for 72 hours ( end in 12:00pm Thursday,
> > > > > 08/05/2016
> > > > ).
> > > > >
> > > > >
> > > > > Please download the release candidate, check the hashes/signature,
> > > > > build it and test it, and then please vote:
> > > > >
> > > > >
> > > > > [ ] +1 approve
> > > > >
> > > > > [ ] +0 no opinion
> > > > >
> > > > > [ ] -1 disapprove (and reason why)
> > > > >
> > > > >
> > > > > +1 from my side for the release.
> > > > >
> > > > > Cheers!
> > > > > --
> > > > > Navina R.
> > > > > navina@apache.org
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Jagadish V,
> > > > Graduate Student,
> > > > Department of Computer Science,
> > > > Stanford University
> > > >
> > >
> > > -----
> > > No virus found in this message.
> > > Checked by AVG - www.avg.com
> > > Version: 2016.0.7688 / Virus Database: 4627/12695 - Release Date:
> > 07/27/16
> > >
> >
> >
> >
> > --
> > Navina R.
> >
>
--
Navina R.
Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
Posted by Yi Pan <ni...@gmail.com>.
Hi, Navina,
Yes. You should put your key in the KEYS file.
And +1 (binding) as I built and ran the zopkio integration test
successfully as well.
On Mon, Aug 1, 2016 at 1:05 PM, Navina Ramesh <nr...@linkedin.com.invalid>
wrote:
> @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.turkington@improvedigital.com> wrote:
>
> > +1 (binding)
> >
> > Built the source ran all tests and tried a sample test job. All looks
> good.
> >
> > One question - 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-----
> > From: Jacob Maes [mailto:jacob.maes@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 <
> > jagadish1989@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
> > > <nramesh@linkedin.com.invalid
> > > > 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**: This release is primarily a bug-fix release with no major
> > > changes
> > > > to the public api. Since we are behind schedule in terms of
> > > > releases, we are combining the DISCUSS and VOTE email into a single
> > > > VOTE email. If anyone has objections, please do raise them. We plan
> > > > to shortly follow-up with a DISCUSS email for 0.11.0 release, that
> > > > brings in new features in multi-threading, REST api etc.
> > > >
> > > >
> > > > The release candidate can be downloaded from here:
> > > > http://home.apache.org/~navina/samza-0.10.1-rc0/
> > > >
> > > >
> > > > The release candidate is signed with pgp key 331C8F69, which can be
> > > > found on keyservers:
> > > > http://pgp.mit.edu/pks/lookup?op=get&search=0x331C8F69
> > > >
> > > >
> > > > The git tag is release-0.10.1-rc0 and signed with the same pgp key:
> > > > *
> > > >
> > > https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1
> > > eb2dc1dbffc661f910b1272b233640
> > > > <
> > > >
> > > https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1
> > > eb2dc1dbffc661f910b1272b233640
> > > > >*
> > > >
> > > >
> > > > Test binaries have been published to Maven's staging repository, and
> > > > are available
> > > > here:
> > > > https://repository.apache.org/content/repositories/orgapachesamza-10
> > > > 12/
> > > >
> > > >
> > > > Note that the binaries were built with JDK7 without incident.
> > > >
> > > > 69 issues were resolved for this release:
> > > >
> > > >
> > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND
> > > %20fixVersion%20in%20(0.10.1)%20AND%20status%20in%20(Resolved%2C%20Clo
> > > sed)
> > > >
> > > >
> > > > The vote will be open for 72 hours ( end in 12:00pm Thursday,
> > > > 08/05/2016
> > > ).
> > > >
> > > >
> > > > Please download the release candidate, check the hashes/signature,
> > > > build it and test it, and then please vote:
> > > >
> > > >
> > > > [ ] +1 approve
> > > >
> > > > [ ] +0 no opinion
> > > >
> > > > [ ] -1 disapprove (and reason why)
> > > >
> > > >
> > > > +1 from my side for the release.
> > > >
> > > > Cheers!
> > > > --
> > > > Navina R.
> > > > navina@apache.org
> > > >
> > >
> > >
> > >
> > > --
> > > Jagadish V,
> > > Graduate Student,
> > > Department of Computer Science,
> > > Stanford University
> > >
> >
> > -----
> > No virus found in this message.
> > Checked by AVG - www.avg.com
> > Version: 2016.0.7688 / Virus Database: 4627/12695 - Release Date:
> 07/27/16
> >
>
>
>
> --
> Navina R.
>
Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
Posted by Julian Hyde <jh...@apache.org>.
+1 (non-binding)
Downloaded, built, ran tests, checked L&N. Instructions on installing gradle were nice and clear.
I ran rat (I presume that ‘./gradlew rat’ is the correct command) and it passed.
I believe that best practice is to put the release bits under https://dist.apache.org/repos/dist/dev/${project}/${release} <https://dist.apache.org/repos/dist/dev/$%7Bproject%7D/$%7Brelease%7D> rather than under home.apache.org <http://home.apache.org/>. I suggest that Samza follows this for future releases.
The best place to put KEYS is https://dist.apache.org/repos/dist/dev/${project}/KEYS <https://dist.apache.org/repos/dist/dev/$%7Bproject%7D/KEYS>, not in git (because git can be subverted).
Should Gemfile.lock be in the release? Isn’t it a generated file?
Julian
> On Aug 1, 2016, at 1:05 PM, Navina Ramesh <nr...@linkedin.com.INVALID> wrote:
>
> @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.turkington@improvedigital.com> wrote:
>
>> +1 (binding)
>>
>> Built the source ran all tests and tried a sample test job. All looks good.
>>
>> One question - 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-----
>> From: Jacob Maes [mailto:jacob.maes@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 <
>> jagadish1989@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
>>> <nramesh@linkedin.com.invalid
>>>> 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**: This release is primarily a bug-fix release with no major
>>> changes
>>>> to the public api. Since we are behind schedule in terms of
>>>> releases, we are combining the DISCUSS and VOTE email into a single
>>>> VOTE email. If anyone has objections, please do raise them. We plan
>>>> to shortly follow-up with a DISCUSS email for 0.11.0 release, that
>>>> brings in new features in multi-threading, REST api etc.
>>>>
>>>>
>>>> The release candidate can be downloaded from here:
>>>> http://home.apache.org/~navina/samza-0.10.1-rc0/
>>>>
>>>>
>>>> The release candidate is signed with pgp key 331C8F69, which can be
>>>> found on keyservers:
>>>> http://pgp.mit.edu/pks/lookup?op=get&search=0x331C8F69
>>>>
>>>>
>>>> The git tag is release-0.10.1-rc0 and signed with the same pgp key:
>>>> *
>>>>
>>> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1
>>> eb2dc1dbffc661f910b1272b233640
>>>> <
>>>>
>>> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1
>>> eb2dc1dbffc661f910b1272b233640
>>>>> *
>>>>
>>>>
>>>> Test binaries have been published to Maven's staging repository, and
>>>> are available
>>>> here:
>>>> https://repository.apache.org/content/repositories/orgapachesamza-10
>>>> 12/
>>>>
>>>>
>>>> Note that the binaries were built with JDK7 without incident.
>>>>
>>>> 69 issues were resolved for this release:
>>>>
>>>>
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND
>>> %20fixVersion%20in%20(0.10.1)%20AND%20status%20in%20(Resolved%2C%20Clo
>>> sed)
>>>>
>>>>
>>>> The vote will be open for 72 hours ( end in 12:00pm Thursday,
>>>> 08/05/2016
>>> ).
>>>>
>>>>
>>>> Please download the release candidate, check the hashes/signature,
>>>> build it and test it, and then please vote:
>>>>
>>>>
>>>> [ ] +1 approve
>>>>
>>>> [ ] +0 no opinion
>>>>
>>>> [ ] -1 disapprove (and reason why)
>>>>
>>>>
>>>> +1 from my side for the release.
>>>>
>>>> Cheers!
>>>> --
>>>> Navina R.
>>>> navina@apache.org
>>>>
>>>
>>>
>>>
>>> --
>>> Jagadish V,
>>> Graduate Student,
>>> Department of Computer Science,
>>> Stanford University
>>>
>>
>> -----
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2016.0.7688 / Virus Database: 4627/12695 - Release Date: 07/27/16
>>
>
>
>
> --
> Navina R.
Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
Posted by Navina Ramesh <nr...@linkedin.com.INVALID>.
@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.turkington@improvedigital.com> wrote:
> +1 (binding)
>
> Built the source ran all tests and tried a sample test job. All looks good.
>
> One question - 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-----
> From: Jacob Maes [mailto:jacob.maes@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 <
> jagadish1989@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
> > <nramesh@linkedin.com.invalid
> > > 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**: This release is primarily a bug-fix release with no major
> > changes
> > > to the public api. Since we are behind schedule in terms of
> > > releases, we are combining the DISCUSS and VOTE email into a single
> > > VOTE email. If anyone has objections, please do raise them. We plan
> > > to shortly follow-up with a DISCUSS email for 0.11.0 release, that
> > > brings in new features in multi-threading, REST api etc.
> > >
> > >
> > > The release candidate can be downloaded from here:
> > > http://home.apache.org/~navina/samza-0.10.1-rc0/
> > >
> > >
> > > The release candidate is signed with pgp key 331C8F69, which can be
> > > found on keyservers:
> > > http://pgp.mit.edu/pks/lookup?op=get&search=0x331C8F69
> > >
> > >
> > > The git tag is release-0.10.1-rc0 and signed with the same pgp key:
> > > *
> > >
> > https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1
> > eb2dc1dbffc661f910b1272b233640
> > > <
> > >
> > https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1
> > eb2dc1dbffc661f910b1272b233640
> > > >*
> > >
> > >
> > > Test binaries have been published to Maven's staging repository, and
> > > are available
> > > here:
> > > https://repository.apache.org/content/repositories/orgapachesamza-10
> > > 12/
> > >
> > >
> > > Note that the binaries were built with JDK7 without incident.
> > >
> > > 69 issues were resolved for this release:
> > >
> > >
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND
> > %20fixVersion%20in%20(0.10.1)%20AND%20status%20in%20(Resolved%2C%20Clo
> > sed)
> > >
> > >
> > > The vote will be open for 72 hours ( end in 12:00pm Thursday,
> > > 08/05/2016
> > ).
> > >
> > >
> > > Please download the release candidate, check the hashes/signature,
> > > build it and test it, and then please vote:
> > >
> > >
> > > [ ] +1 approve
> > >
> > > [ ] +0 no opinion
> > >
> > > [ ] -1 disapprove (and reason why)
> > >
> > >
> > > +1 from my side for the release.
> > >
> > > Cheers!
> > > --
> > > Navina R.
> > > navina@apache.org
> > >
> >
> >
> >
> > --
> > Jagadish V,
> > Graduate Student,
> > Department of Computer Science,
> > Stanford University
> >
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2016.0.7688 / Virus Database: 4627/12695 - Release Date: 07/27/16
>
--
Navina R.
RE: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
Posted by Garry Turkington <g....@improvedigital.com>.
+1 (binding)
Built the source ran all tests and tried a sample test job. All looks good.
One question - 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-----
From: Jacob Maes [mailto:jacob.maes@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 < jagadish1989@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
> <nramesh@linkedin.com.invalid
> > 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**: This release is primarily a bug-fix release with no major
> changes
> > to the public api. Since we are behind schedule in terms of
> > releases, we are combining the DISCUSS and VOTE email into a single
> > VOTE email. If anyone has objections, please do raise them. We plan
> > to shortly follow-up with a DISCUSS email for 0.11.0 release, that
> > brings in new features in multi-threading, REST api etc.
> >
> >
> > The release candidate can be downloaded from here:
> > http://home.apache.org/~navina/samza-0.10.1-rc0/
> >
> >
> > The release candidate is signed with pgp key 331C8F69, which can be
> > found on keyservers:
> > http://pgp.mit.edu/pks/lookup?op=get&search=0x331C8F69
> >
> >
> > The git tag is release-0.10.1-rc0 and signed with the same pgp key:
> > *
> >
> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1
> eb2dc1dbffc661f910b1272b233640
> > <
> >
> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1
> eb2dc1dbffc661f910b1272b233640
> > >*
> >
> >
> > Test binaries have been published to Maven's staging repository, and
> > are available
> > here:
> > https://repository.apache.org/content/repositories/orgapachesamza-10
> > 12/
> >
> >
> > Note that the binaries were built with JDK7 without incident.
> >
> > 69 issues were resolved for this release:
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND
> %20fixVersion%20in%20(0.10.1)%20AND%20status%20in%20(Resolved%2C%20Clo
> sed)
> >
> >
> > The vote will be open for 72 hours ( end in 12:00pm Thursday,
> > 08/05/2016
> ).
> >
> >
> > Please download the release candidate, check the hashes/signature,
> > build it and test it, and then please vote:
> >
> >
> > [ ] +1 approve
> >
> > [ ] +0 no opinion
> >
> > [ ] -1 disapprove (and reason why)
> >
> >
> > +1 from my side for the release.
> >
> > Cheers!
> > --
> > Navina R.
> > navina@apache.org
> >
>
>
>
> --
> Jagadish V,
> Graduate Student,
> Department of Computer Science,
> Stanford University
>
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2016.0.7688 / Virus Database: 4627/12695 - Release Date: 07/27/16
Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
Posted by Jacob Maes <ja...@gmail.com>.
+1 non-binding
Lots of good fixes in this release.
On Mon, Aug 1, 2016 at 11:41 AM, Jagadish Venkatraman <
jagadish1989@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
> <nramesh@linkedin.com.invalid
> > 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**: This release is primarily a bug-fix release with no major
> changes
> > to the public api. Since we are behind schedule in terms of releases, we
> > are combining the DISCUSS and VOTE email into a single VOTE email. If
> > anyone has objections, please do raise them. We plan to shortly follow-up
> > with a DISCUSS email for 0.11.0 release, that brings in new features in
> > multi-threading, REST api etc.
> >
> >
> > The release candidate can be downloaded from here:
> > http://home.apache.org/~navina/samza-0.10.1-rc0/
> >
> >
> > The release candidate is signed with pgp key 331C8F69, which can be found
> > on keyservers:
> > http://pgp.mit.edu/pks/lookup?op=get&search=0x331C8F69
> >
> >
> > The git tag is release-0.10.1-rc0 and signed with the same pgp key:
> > *
> >
> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1eb2dc1dbffc661f910b1272b233640
> > <
> >
> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1eb2dc1dbffc661f910b1272b233640
> > >*
> >
> >
> > Test binaries have been published to Maven's staging repository, and
> > are available
> > here:
> > https://repository.apache.org/content/repositories/orgapachesamza-1012/
> >
> >
> > Note that the binaries were built with JDK7 without incident.
> >
> > 69 issues were resolved for this release:
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND%20fixVersion%20in%20(0.10.1)%20AND%20status%20in%20(Resolved%2C%20Closed)
> >
> >
> > The vote will be open for 72 hours ( end in 12:00pm Thursday, 08/05/2016
> ).
> >
> >
> > Please download the release candidate, check the hashes/signature, build
> > it and
> > test it, and then please vote:
> >
> >
> > [ ] +1 approve
> >
> > [ ] +0 no opinion
> >
> > [ ] -1 disapprove (and reason why)
> >
> >
> > +1 from my side for the release.
> >
> > Cheers!
> > --
> > Navina R.
> > navina@apache.org
> >
>
>
>
> --
> Jagadish V,
> Graduate Student,
> Department of Computer Science,
> Stanford University
>
Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
Posted by xinyu liu <xi...@gmail.com>.
+1 (non-binding).
Thanks,
Xinyu
On Mon, Aug 1, 2016 at 11:41 AM, Jagadish Venkatraman <
jagadish1989@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
> <nramesh@linkedin.com.invalid
> > 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**: This release is primarily a bug-fix release with no major
> changes
> > to the public api. Since we are behind schedule in terms of releases, we
> > are combining the DISCUSS and VOTE email into a single VOTE email. If
> > anyone has objections, please do raise them. We plan to shortly follow-up
> > with a DISCUSS email for 0.11.0 release, that brings in new features in
> > multi-threading, REST api etc.
> >
> >
> > The release candidate can be downloaded from here:
> > http://home.apache.org/~navina/samza-0.10.1-rc0/
> >
> >
> > The release candidate is signed with pgp key 331C8F69, which can be found
> > on keyservers:
> > http://pgp.mit.edu/pks/lookup?op=get&search=0x331C8F69
> >
> >
> > The git tag is release-0.10.1-rc0 and signed with the same pgp key:
> > *
> >
> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1eb2dc1dbffc661f910b1272b233640
> > <
> >
> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1eb2dc1dbffc661f910b1272b233640
> > >*
> >
> >
> > Test binaries have been published to Maven's staging repository, and
> > are available
> > here:
> > https://repository.apache.org/content/repositories/orgapachesamza-1012/
> >
> >
> > Note that the binaries were built with JDK7 without incident.
> >
> > 69 issues were resolved for this release:
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND%20fixVersion%20in%20(0.10.1)%20AND%20status%20in%20(Resolved%2C%20Closed)
> >
> >
> > The vote will be open for 72 hours ( end in 12:00pm Thursday, 08/05/2016
> ).
> >
> >
> > Please download the release candidate, check the hashes/signature, build
> > it and
> > test it, and then please vote:
> >
> >
> > [ ] +1 approve
> >
> > [ ] +0 no opinion
> >
> > [ ] -1 disapprove (and reason why)
> >
> >
> > +1 from my side for the release.
> >
> > Cheers!
> > --
> > Navina R.
> > navina@apache.org
> >
>
>
>
> --
> Jagadish V,
> Graduate Student,
> Department of Computer Science,
> Stanford University
>
Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
Posted by Jagadish Venkatraman <ja...@gmail.com>.
Thanks for driving this release.+1 approve (non-binding)
Thanks,
Jagadish
On Mon, Aug 1, 2016 at 11:39 AM, Navina Ramesh <nramesh@linkedin.com.invalid
> 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**: This release is primarily a bug-fix release with no major changes
> to the public api. Since we are behind schedule in terms of releases, we
> are combining the DISCUSS and VOTE email into a single VOTE email. If
> anyone has objections, please do raise them. We plan to shortly follow-up
> with a DISCUSS email for 0.11.0 release, that brings in new features in
> multi-threading, REST api etc.
>
>
> The release candidate can be downloaded from here:
> http://home.apache.org/~navina/samza-0.10.1-rc0/
>
>
> The release candidate is signed with pgp key 331C8F69, which can be found
> on keyservers:
> http://pgp.mit.edu/pks/lookup?op=get&search=0x331C8F69
>
>
> The git tag is release-0.10.1-rc0 and signed with the same pgp key:
> *
> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1eb2dc1dbffc661f910b1272b233640
> <
> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1eb2dc1dbffc661f910b1272b233640
> >*
>
>
> Test binaries have been published to Maven's staging repository, and
> are available
> here:
> https://repository.apache.org/content/repositories/orgapachesamza-1012/
>
>
> Note that the binaries were built with JDK7 without incident.
>
> 69 issues were resolved for this release:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND%20fixVersion%20in%20(0.10.1)%20AND%20status%20in%20(Resolved%2C%20Closed)
>
>
> The vote will be open for 72 hours ( end in 12:00pm Thursday, 08/05/2016 ).
>
>
> Please download the release candidate, check the hashes/signature, build
> it and
> test it, and then please vote:
>
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove (and reason why)
>
>
> +1 from my side for the release.
>
> Cheers!
> --
> Navina R.
> navina@apache.org
>
--
Jagadish V,
Graduate Student,
Department of Computer Science,
Stanford University