> 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/
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50682/
---
(Updated Aug. 2, 2016, 12:39 a.m.)
Review request for samza, Boris Shkolnik, Ch
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50682/#review144420
---
Ship it!
Ship It!
- Fred Ji
On Aug. 2, 2016, 12:13 a.m., Jak
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
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50682/#review144417
---
Ship it!
+1. thanks for the quick fix!
- Xinyu Liu
On Aug. 2
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50682/#review144414
---
Ship it!
Ship It!
- Navina Ramesh
On Aug. 2, 2016, 12:13 a.m
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50682/
---
Review request for samza, Boris Shkolnik, Chris Pettitt, Fred Ji, Jake Maes,
Nav
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50670/
---
(Updated Aug. 1, 2016, 11:29 p.m.)
Review request for samza, Yi Pan (Data Infra
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
wrote:
> @Garry: Yeah. I wasn't very clear about it either.
>
> @Yi: Do you know if it is a part of the
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50670/#review144393
---
Ship it!
+1
- Xinyu Liu
On Aug. 1, 2016, 10:21 p.m., Jagadis
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50670/#review144391
---
samza-yarn/src/main/scala/org/apache/samza/job/yarn/SamzaAppMaste
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50670/
---
(Updated Aug. 1, 2016, 10:21 p.m.)
Review request for samza, Yi Pan (Data Infra
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50670/#review144387
---
samza-yarn/src/main/scala/org/apache/samza/job/yarn/SamzaAppMaste
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50670/
---
Review request for samza, Yi Pan (Data Infrastructure), Navina Ramesh, and
Xinyu
+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/d
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
@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.turking...@improvedigital.com> wrote:
> +1 (binding)
>
> Built the source ran all
+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:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50667/#review144372
---
Ship it!
Ship It!
- Yi Pan (Data Infrastructure)
On Aug. 1,
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50667/
---
Review request for samza, Boris Shkolnik, Chris Pettitt, Fred Ji, Jake Maes,
Nav
+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
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50583/#review144369
---
Ship it!
Ship It!
- Yi Pan (Data Infrastructure)
On July 28,
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50317/#review144365
---
Ship it!
Ship It!
- Yi Pan (Data Infrastructure)
On July 22,
26 matches
Mail list logo
