Resent the CANCEL email, hopefully it makes it this time.
- Prateek
On Wed, May 17, 2017 at 2:08 PM, Navina Ramesh (Apache)
wrote:
> Prateek told me that he sent out a cancel email. It didn't reach the
> mail-archive I think. Lately, we have this kind of issues where the emails
> are not reachi
Prateek told me that he sent out a cancel email. It didn't reach the
mail-archive I think. Lately, we have this kind of issues where the emails
are not reaching our dev list.
On Wed, May 17, 2017 at 2:06 PM, Yi Pan wrote:
> Hi, all,
>
> Based on the conversation above, can we officially cancel t
Prateek told me that he sent out a cancel email. It didn't reach the
mail-archive I think. Lately, we have this kind of issues where the emails
are not reaching our dev list.
On Wed, May 17, 2017 at 2:06 PM, Yi Pan wrote:
> Hi, all,
>
> Based on the conversation above, can we officially cancel t
Hi, all,
Based on the conversation above, can we officially cancel this vote?
Thanks!
-Yi
On Mon, May 15, 2017 at 9:31 AM, Ignacio Solis wrote:
> Thanks!
>
> On Mon, May 15, 2017 at 8:00 AM, Navina Ramesh
> wrote:
> > I will try to get the patch out today. Work doesn't look trivial. I am on
Thanks!
On Mon, May 15, 2017 at 8:00 AM, Navina Ramesh
wrote:
> I will try to get the patch out today. Work doesn't look trivial. I am on
> it.
>
> Navina
>
> On May 14, 2017 23:10, "Ignacio Solis" wrote:
>
>> We should hold off until it is solved. How long will it take to fix this?
>>
>> On Su
I will try to get the patch out today. Work doesn't look trivial. I am on
it.
Navina
On May 14, 2017 23:10, "Ignacio Solis" wrote:
> We should hold off until it is solved. How long will it take to fix this?
>
> On Sun, May 14, 2017 at 10:13 PM, Navina Ramesh (Apache)
> wrote:
> > I just chang
We should hold off until it is solved. How long will it take to fix this?
On Sun, May 14, 2017 at 10:13 PM, Navina Ramesh (Apache)
wrote:
> I just changed the status of this JIRA to "BLOCKER" -
> https://issues.apache.org/jira/browse/SAMZA-1128
>
> This causes a bug in standalone deployment wher
I just changed the status of this JIRA to "BLOCKER" -
https://issues.apache.org/jira/browse/SAMZA-1128
This causes a bug in standalone deployment where any failure in the barrier
protocol stops the scheduled executorservice. Unfortunately,
CoordinationUtils creates its own scheduled executorservic
I think we need to add SAMZA-1286 and
SAMZA-1279 to the release .
On Wed, May 10, 2017 at 7:51 PM, Jagadish Venkatraman
wrote:
> This is a call for a vote on a release of Apache Samza 0.13.0. Thanks to
> everyone who has contributed to this release. We are very glad to see some
> new contributor
This is a call for a vote on a release of Apache Samza 0.13.0. Thanks to
everyone who has contributed to this release. We are very glad to see some
new contributors and features in this release.
The release candidate can be downloaded from here:
http://home.apache.org/~jagadish/samza-0.13.0-rc0/
10 matches
Mail list logo