Hi
> On Jun 10, 2557 BE, at 8:48 AM, "John D. Ament"
> wrote:
>
> Joe,
>
>> On Thu, Jun 5, 2014 at 11:20 PM, Joe Brockmeier wrote:
>>> On 06/01/2014 01:31 PM, Marvin Humphrey wrote:
>>> Joe Brockmeier wrote:
>>>
I'd be interested in helping this month, with an eye to doing the report
>>
I'm going to put this up on the wiki, please let me know if there are
any issues.
On Tue, Jun 10, 2014, at 01:07 AM, Joe Brockmeier wrote:
> On 06/09/2014 11:11 AM, John D. Ament wrote:
> > All,
> >
> > Please find the draft board report which includes all podlings that
> > have submitted report
The only thing I've noticed is that the dates of the releases are
missing. I'm not sure that's a big requirement though.
On Tue, Jun 10, 2014 at 12:35 PM, Joe Brockmeier wrote:
> I'm going to put this up on the wiki, please let me know if there are
> any issues.
>
> On Tue, Jun 10, 2014, at 01:0
On Tue, Jun 10, 2014, at 11:40 AM, John D. Ament wrote:
> The only thing I've noticed is that the dates of the releases are
> missing. I'm not sure that's a big requirement though.
You mean the final release date, or the length of the vote? Marvin had
said that was optional (length of vote) and I
We're currently working on the first release for Samza and have run into a
problem involving the source release and our build system, Gradle. Both
DataFu and Aurora use Gradle and will run into this issue as well when they
do a source release.
Gradle provides a wrapper script, gradlew that allows
On Tue, Jun 10, 2014 at 1:18 PM, Jakob Homan wrote:
> I'm thinking we should make an exception to this no-jar rule for the
> gradlew jar. The Gradle project is open source [3], Apache 2 licensed [4]
> and intends for this jar to be included as part of the source of projects
> [1]. Finally, the j
Hey Jakob
We did run into this while packaging our first rc in Aurora. There was some
discussion around this on our dev list and we ended up removed the
gradle.jar and gradlew from the source dist and added the wrapper task to
build.gradle so it will always generate the same gradlew that we have
co
On Tue, Jun 10, 2014 at 9:35 AM, Joe Brockmeier wrote:
> I'm going to put this up on the wiki, please let me know if there are
> any issues.
The editorial copy looks good to me!
It seems as though the summary may have been submitted in an
unfinished state -- many podlings were missing and some t
On Tue, Jun 10, 2014 at 9:46 AM, Joe Brockmeier wrote:
> On Tue, Jun 10, 2014, at 11:40 AM, John D. Ament wrote:
>> The only thing I've noticed is that the dates of the releases are
>> missing. I'm not sure that's a big requirement though.
>
> You mean the final release date, or the length of the
Marvin,
What do you think about listing storm under ready to graduate instead
of community growth?
John
On Tue, Jun 10, 2014 at 9:04 PM, Marvin Humphrey wrote:
> On Tue, Jun 10, 2014 at 9:35 AM, Joe Brockmeier wrote:
>> I'm going to put this up on the wiki, please let me know if there are
>> a
On Tue, Jun 10, 2014 at 6:13 PM, John D. Ament wrote:
> Marvin,
>
> What do you think about listing storm under ready to graduate instead
> of community growth?
Sounds fine. They list a couple of TODOs, but graduation is clearly in
sight. Let's go with your judgment.
Marvin Humphrey
--
On Tue, Jun 10, 2014 at 9:17 PM, Marvin Humphrey wrote:
> On Tue, Jun 10, 2014 at 6:13 PM, John D. Ament wrote:
>> Marvin,
>>
>> What do you think about listing storm under ready to graduate instead
>> of community growth?
>
> Sounds fine. They list a couple of TODOs, but graduation is clearly in
Drill should probably be in that category as well.
300 issues resolved last 30 days, lots of contributors.
They have about as much stuff happening as HBase.
On Tue, Jun 10, 2014 at 6:13 PM, John D. Ament
wrote:
> Marvin,
>
> What do you think about listing storm under ready to graduate inste
Sorry one other thing. Should we remove podlings not reporting from the TOC?
On Tue, Jun 10, 2014 at 9:22 PM, John D. Ament wrote:
> On Tue, Jun 10, 2014 at 9:17 PM, Marvin Humphrey
> wrote:
>> On Tue, Jun 10, 2014 at 6:13 PM, John D. Ament
>> wrote:
>>> Marvin,
>>>
>>> What do you think abo
On Tue, Jun 10, 2014 at 9:28 PM, Ted Dunning wrote:
> Drill should probably be in that category as well.
>
> 300 issues resolved last 30 days, lots of contributors.
>
> They have about as much stuff happening as HBase.
>
They're already there, but generally agreed. I am concerned that
their repo
On Tue, Jun 10, 2014 at 6:33 PM, John D. Ament
wrote:
> On Tue, Jun 10, 2014 at 9:28 PM, Ted Dunning
> wrote:
> > Drill should probably be in that category as well.
> >
> > 300 issues resolved last 30 days, lots of contributors.
> >
> > They have about as much stuff happening as HBase.
> >
>
> T
On Mon, Jun 9, 2014 at 9:11 AM, John D. Ament wrote:
> Please find the draft board report which includes all podlings that
> have submitted reports thus far below.
In future months, I hope that we are able to get to the task of podling report
normalization before submitting the draft to general@
On Tue, Jun 10, 2014 at 6:22 PM, John D. Ament wrote:
> One other item. RE S4 & Retirement, currently the dev list is voting
> on retirement. Is it worth noting that the vote is underway to
> retire?
It's in the report that retirement is being discussed. That's good
enough IMO -- it was the in
On Tue, Jun 10, 2014 at 9:49 PM, Marvin Humphrey wrote:
> On Mon, Jun 9, 2014 at 9:11 AM, John D. Ament wrote:
>
>> Please find the draft board report which includes all podlings that
>> have submitted reports thus far below.
>
> In future months, I hope that we are able to get to the task of pod
19 matches
Mail list logo
