The Apache Jenkins build system has built Sentry-jdk-1.7 (build #648)
Status: Fixed
Check console output at https://builds.apache.org/job/Sentry-jdk-1.7/648/ to
view the results.
> On May 2, 2016, 9:45 p.m., Gregory Chanan wrote:
> > Why put the caching at the client layer instead of the provider backend
> > layer? It seems unlikely to me that the average client actually wants
> > caching or need caching, whereas an arbitrary external service probably
> > does.
>
> A
Thanks a lot Sravya! This is really pretty useful. One comment for the
dashboard: similar to code review queues, can we have a label or status for
“Design Review” to track the new features Jira that have designs need to be
reviewed?
Best,
Hao
On Mon, May 2, 2016 at 6:35 PM, Sravya Tirukkovalur
w
Hi all,
Thought it might be useful to have a dashboard that we all share for the
project to understand what is on the review and triage queues. We can also
use it to facilitate our monthly hangouts. Here is a link. Please let me
know what else you would like to see.
https://issues.apache.org/jira/
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/46909/#review131419
---
Note: these comments are based on the assumption you are implement
> On May 2, 2016, 9:45 p.m., Gregory Chanan wrote:
> > Why put the caching at the client layer instead of the provider backend
> > layer? It seems unlikely to me that the average client actually wants
> > caching or need caching, whereas an arbitrary external service probably
> > does.
>
> A
The Apache Jenkins build system has built Sentry-jdk-1.7 (build #647)
Status: Failure
Check console output at https://builds.apache.org/job/Sentry-jdk-1.7/647/ to
view the results.
> On May 2, 2016, 9:45 p.m., Gregory Chanan wrote:
> > Why put the caching at the client layer instead of the provider backend
> > layer? It seems unlikely to me that the average client actually wants
> > caching or need caching, whereas an arbitrary external service probably
> > does.
>
> A
> On May 2, 2016, 9:45 p.m., Gregory Chanan wrote:
> > Why put the caching at the client layer instead of the provider backend
> > layer? It seems unlikely to me that the average client actually wants
> > caching or need caching, whereas an arbitrary external service probably
> > does.
>
> A
> On May 2, 2016, 9:45 p.m., Gregory Chanan wrote:
> > Why put the caching at the client layer instead of the provider backend
> > layer? It seems unlikely to me that the average client actually wants
> > caching or need caching, whereas an arbitrary external service probably
> > does.
>
> A
> On May 2, 2016, 9:45 p.m., Gregory Chanan wrote:
> > Why put the caching at the client layer instead of the provider backend
> > layer? It seems unlikely to me that the average client actually wants
> > caching or need caching, whereas an arbitrary external service probably
> > does.
Any a
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/46912/#review131389
---
Ship it!
Ship It!
- Vamsee Yarlagadda
On May 2, 2016, 9:57 p
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/46912/
---
Review request for sentry and Vamsee Yarlagadda.
Repository: sentry
Descripti
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/46909/#review131381
---
Why put the caching at the client layer instead of the provider ba
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/46909/
---
Review request for sentry, Dapeng Sun, Gregory Chanan, Hao Hao, and Sravya
Tiruk
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/46886/
---
Review request for sentry and Dapeng Sun.
Repository: sentry
Description
16 matches
Mail list logo
