Hi,
Notice that my shepherd report (for Kalumet) has been removed as it did not
report - should this be the case? If a podling fails to report should shepherd
not bother to do a review?
Thanks,
Justin
-
To unsubscribe, e-mail:
On Mon, Jun 9, 2014 at 5:46 AM, Robert Metzger wrote:
> The reasoning behind this was that our project was ready to release a new
> version but the Apache infrastructure was not yet set up.
> Therefore, we decided (together with our mentors) to make a release outside
> Apache, while being formally
On Wed, Jun 11, 2014 at 12:21 AM, Justin Mclean
wrote:
> Notice that my shepherd report (for Kalumet) has been removed as it did not
> report - should this be the case? If a podling fails to report should
> shepherd not bother to do a review?
Thanks for the your consistently excellent shepherdin
Hi!
first of all, let me start with, once again, expressing
tremendous gratitude to our report managers: John
and Marvin. Solid (and at times not quite appreciated)
work!
One thing that I noticed in the report is that the detailed
metrics around releases are missing. Do folks think
there's a valu
On Wed, Jun 11, 2014 at 1:38 PM, Roman Shaposhnik wrote:
> One thing that I noticed in the report is that the detailed
> metrics around releases are missing. Do folks think
> there's a value in having them?
>
What metrics do you mean?
The metrics that really matter are up-take of the new versio
On Wed, Jun 11, 2014 at 1:50 PM, Ted Dunning wrote:
> On Wed, Jun 11, 2014 at 1:38 PM, Roman Shaposhnik wrote:
>
>> One thing that I noticed in the report is that the detailed
>> metrics around releases are missing. Do folks think
>> there's a value in having them?
Here are the metrics that were
In my honest opinion. Last month, I shepherd HDT. They had a 13 day
window and to me this was something that needed to be visualized. I
think the metrics adds clarity to everyone about a problem around
votes.
John
On Wed, Jun 11, 2014 at 4:55 PM, Roman Shaposhnik wrote:
> On Wed, Jun 11, 2014
Good point. Thanks for clarifying.
Yes. I think that those metrics are an excellent measure of community
health.
On Wed, Jun 11, 2014 at 1:55 PM, Roman Shaposhnik wrote:
> On Wed, Jun 11, 2014 at 1:50 PM, Ted Dunning
> wrote:
> > On Wed, Jun 11, 2014 at 1:38 PM, Roman Shaposhnik
> wrote:
On Wed, Jun 11, 2014 at 1:38 PM, Roman Shaposhnik wrote:
> first of all, let me start with, once again, expressing
> tremendous gratitude to our report managers: John
> and Marvin. Solid (and at times not quite appreciated)
> work!
Please add Joe Brockmeier to that list. Thanks for joining us,
On Wed, Jun 11, 2014 at 2:50 PM, Marvin Humphrey wrote:
> On Wed, Jun 11, 2014 at 1:38 PM, Roman Shaposhnik wrote:
>
>> first of all, let me start with, once again, expressing
>> tremendous gratitude to our report managers: John
>> and Marvin. Solid (and at times not quite appreciated)
>> work!
>
Hi!
I would like to kindly request some assistance
from the mentors of the following projects: devicemap,
kalumet, s4, wave and npanday (all CCed).
I would like to figure out whether the concerns I have
for these projects are justified and if they are, what
would be the proposed steps for the IPM
Hey Roman
Why not take them from the voting status page [1], and looks like its
started to fall behind again. I'll go through and clean up again over the
next couple days
-Jake
[1]: http://people.apache.org/~brane/incubator/votes.html
On Wed, Jun 11, 2014 at 6:26 PM, Roman Shaposhnik wrote:
>
On Wed, Jun 11, 2014 at 5:13 PM, Jake Farrell wrote:
> Why not take them from the voting status page [1], and looks like its
> started to fall behind again. I'll go through and clean up again over the
> next couple days
IMO, the voting status page has achieved its purpose and should be
retired.
Seems like NPanday should go to attic. One mentor I asked did not even
monitor it anymore
On Wednesday, June 11, 2014, Roman Shaposhnik wrote:
> Hi!
>
> I would like to kindly request some assistance
> from the mentors of the following projects: devicemap,
> kalumet, s4, wave and npanday (all CC
14 matches
Mail list logo