[ANNOUNCE] Apache MXNet (incubating) 0.12.0 Release

[Chris Olivier]

Hello All,



The Apache MXNet (incubating) Community is happy to announce the
availability of Apache MXNet (incubating) version 0.12!



Contributors in the MXNet community have collaborated to bring such feature
enhancements to users. With this release, MXNet adds two new important
features:

• Support for NVIDIA Volta GPUs, which enables users to dramatically reduce
the training and inference time for a neural network model

• Support for Sparse Tensors, which enables users to train a model with
sparse matrices in a storage and compute-efficient manner



Apache MXNet (incubating) is a deep learning framework designed for both
efficiency and flexibility. It allows you to mix symbolic and imperative
programming to maximize efficiency and productivity.



A full list of the changes in this release can be found in the release
notes:

https://cwiki.apache.org/confluence/display/MXNET/MXNet+0.12.0+Release+Notes



A Link to the Download is here: http://www.apache.org/dist/incubator/mxnet/



If you prefer to build from source and experiment with various compile-time
configuration options, use this link to get the instructions:

http://mxnet.incubator.apache.org/install/index.html



Or You can download and play with MXNet easily using one of the options
below:

   1. The Pip package can be found here: https://pypi.python.org/pypi/mxnet
   2. The Docker Images can be found here: https://hub.docker.com/u/mxnet/



The release tag used for the v0.12 release is:

https://github.com/apache/incubator-mxnet/tree/0.12.0/



Some more MXNet Resources –

   1. Issues: https://github.com/apache/incubator-mxnet/issues
   2. Wiki: https://cwiki.apache.org/confluence/display/MXNET



If you want to learn more about MXNet visit http://mxnet.incubator.a
pache.org/

Finally, you are welcome to join and also invite your friends to the
dynamic and growing MXNet community by subscribing to
d...@mxnet.incubator.apache.org



Note: You will have to clear your browser cache in order to view the
website updates (Instructions here
)



Thanks!

Apache MXNet (incubating) Team

___



DISCLAIMER:

Apache MXNet (incubating) is an effort undergoing incubation at The

Apache Software Foundation (ASF), sponsored by the name of Apache

Incubator PMC. Incubation is required of all newly accepted

projects until a further review indicates that the

infrastructure, communications, and decision making process have

stabilized in a manner consistent with other successful ASF

projects. While incubation status is not necessarily a reflection

of the completeness or stability of the code, it does indicate

that the project has yet to be fully endorsed by the ASF.

Re: Daffodil Nov 2017 Podling Report

[John D. Ament]

Added, happy editing!

On Wed, Nov 1, 2017 at 12:11 PM Taylor Wise  wrote:

> It's TaylorWise
>
> Thanks!
>
> On 2017-11-01 09:18, "John D. Ament"  wrote:
> > Taylor
> >
> > What is your wiki username?
> >
> > On Nov 1, 2017 9:18 AM, "Taylor Wise"  wrote:
> >
> > > Greetings,
> > >
> > >
> > > Could I receive write access to the wiki to add the Nov 2017 podling
> > > report for Daffodil?
> > >
> > >
> > > Thanks!
> > >
> > >
> > > -Taylor Wise
> > >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Daffodil Nov 2017 Podling Report

[Taylor Wise]

It's TaylorWise

Thanks!

On 2017-11-01 09:18, "John D. Ament"  wrote: 
> Taylor
> 
> What is your wiki username?
> 
> On Nov 1, 2017 9:18 AM, "Taylor Wise"  wrote:
> 
> > Greetings,
> >
> >
> > Could I receive write access to the wiki to add the Nov 2017 podling
> > report for Daffodil?
> >
> >
> > Thanks!
> >
> >
> > -Taylor Wise
> >
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Resolution to graduate Apache Impala to TLP

[Jim Apple]

My methodology was to make it opt-out - I discussed this with one of
our mentors, todd@, and he viewed it as a good way to go about it. I
emailed all PPMC members and mentors to ask if they wanted to be on
the PMC, letting them know that if they said nothing they would be
included, and that they could resign at any time, present or future. I
got one "no", 17 "yes", and seven non-responses. I know that three of
the non-responders are people who want to be on the PMC (we have
spoken about it).

On Wed, Nov 1, 2017 at 7:45 AM, Mike Drob  wrote:
> Hi Jim, have you verified with all of the proposed members that they would
> like to continue on with the project once it completes incubation?
>
> On Tue, Oct 31, 2017 at 11:38 PM, Jim Apple  wrote:
>
>> The Impala community has discussed and voted positively on graduating
>> to a TLP. Following the instructions from the graduation guide, this
>> thread is for discussion.
>>
>> Community Discussion:
>> https://lists.apache.org/thread.html/2f5db4788aff9b0557354b9106c032
>> 8a29c1f90c1a74a228163949d2@%3Cdev.impala.apache.org%3E
>>
>> Community Vote:
>> https://lists.apache.org/thread.html/a5a7c6895b3e019347d6e4e4cf49d6
>> 7d094d31b8f2c7b4d59200f3e4@%3Cdev.impala.apache.org%3E
>>
>> Resolution:
>>
>> Establish the Apache Impala Project
>>
>> WHEREAS, the Board of Directors deems it to be in the best interests of
>> the Foundation and consistent with the Foundation's purpose to establish
>> a Project Management Committee charged with the creation and maintenance
>> of open-source software, for distribution at no charge to the public,
>> related to a high-performance distributed SQL engine.
>>
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>> (PMC), to be known as the "Apache Impala Project", be and hereby is
>> established pursuant to Bylaws of the Foundation; and be it further
>>
>> RESOLVED, that the Apache Impala Project be and hereby is responsible
>> for the creation and maintenance of software related to a
>> high-performance distributed SQL engine; and be it further
>>
>> RESOLVED, that the office of "Vice President, Apache Impala" be and
>> hereby is created, the person holding such office to serve at the
>> direction of the Board of Directors as the chair of the Apache Impala
>> Project, and to have primary responsibility for management of the
>> projects within the scope of responsibility of the Apache Impala
>> Project; and be it further
>>
>> RESOLVED, that the persons listed immediately below be and hereby are
>> appointed to serve as the initial members of the Apache Impala Project:
>>
>> * Alex Behm 
>> * Bharath Vissapragada 
>> * Brock Noland 
>> * Carl Steinbach 
>> * Casey Ching 
>> * Daniel Hecht 
>> * Dimitris Tsirogiannis 
>> * Henry Robinson 
>> * Ishaan Joshi 
>> * Jim Apple 
>> * John Russell 
>> * Juan Yu 
>> * Lars Volker 
>> * Lenni Kuff 
>> * Marcel Kornacker 
>> * Martin Grund 
>> * Matthew Jacobs 
>> * Michael Brown 
>> * Michael Ho 
>> * Sailesh Mukil 
>> * Skye Wanderman-Milne 
>> * Taras Bobrovytsky 
>> * Tim Armstrong 
>> * Todd Lipcon 
>>
>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jim Apple be appointed to
>> the office of Vice President, Apache Impala, to serve in accordance with
>> and subject to the direction of the Board of Directors and the Bylaws of
>> the Foundation until death, resignation, retirement, removal or
>> disqualification, or until a successor is appointed; and be it further
>>
>> RESOLVED, that the initial Apache Impala PMC be and hereby is tasked
>> with the creation of a set of bylaws intended to encourage open
>> development and increased participation in the Apache Impala Project;
>> and be it further
>>
>> RESOLVED, that the Apache Impala Project be and hereby is tasked with
>> the migration and rationalization of the Apache Incubator Impala
>> podling; and be it further
>>
>> RESOLVED, that all responsibilities pertaining to the Apache Incubator
>> Impala podling encumbered upon the Apache Incubator PMC are hereafter
>> discharged.
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Resolution to graduate Apache Impala to TLP

[Mike Drob]

Hi Jim, have you verified with all of the proposed members that they would
like to continue on with the project once it completes incubation?

On Tue, Oct 31, 2017 at 11:38 PM, Jim Apple  wrote:

> The Impala community has discussed and voted positively on graduating
> to a TLP. Following the instructions from the graduation guide, this
> thread is for discussion.
>
> Community Discussion:
> https://lists.apache.org/thread.html/2f5db4788aff9b0557354b9106c032
> 8a29c1f90c1a74a228163949d2@%3Cdev.impala.apache.org%3E
>
> Community Vote:
> https://lists.apache.org/thread.html/a5a7c6895b3e019347d6e4e4cf49d6
> 7d094d31b8f2c7b4d59200f3e4@%3Cdev.impala.apache.org%3E
>
> Resolution:
>
> Establish the Apache Impala Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a high-performance distributed SQL engine.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Impala Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Impala Project be and hereby is responsible
> for the creation and maintenance of software related to a
> high-performance distributed SQL engine; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Impala" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache Impala
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Impala
> Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache Impala Project:
>
> * Alex Behm 
> * Bharath Vissapragada 
> * Brock Noland 
> * Carl Steinbach 
> * Casey Ching 
> * Daniel Hecht 
> * Dimitris Tsirogiannis 
> * Henry Robinson 
> * Ishaan Joshi 
> * Jim Apple 
> * John Russell 
> * Juan Yu 
> * Lars Volker 
> * Lenni Kuff 
> * Marcel Kornacker 
> * Martin Grund 
> * Matthew Jacobs 
> * Michael Brown 
> * Michael Ho 
> * Sailesh Mukil 
> * Skye Wanderman-Milne 
> * Taras Bobrovytsky 
> * Tim Armstrong 
> * Todd Lipcon 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jim Apple be appointed to
> the office of Vice President, Apache Impala, to serve in accordance with
> and subject to the direction of the Board of Directors and the Bylaws of
> the Foundation until death, resignation, retirement, removal or
> disqualification, or until a successor is appointed; and be it further
>
> RESOLVED, that the initial Apache Impala PMC be and hereby is tasked
> with the creation of a set of bylaws intended to encourage open
> development and increased participation in the Apache Impala Project;
> and be it further
>
> RESOLVED, that the Apache Impala Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Impala
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Impala podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[RESULT] [VOTE] Accept Crail into the Apache Incubator

[Craig Russell]

Subject line change to close the vote.

> On Nov 1, 2017, at 6:42 AM, Luciano Resende  wrote:
> 
> On Thu, Oct 26, 2017 at 8:31 AM, Luciano Resende 
> wrote:
> 
>> Now that the discussion thread on the Crail proposal has ended, please
>> vote on accepting Crail into into the Apache Incubator.
>> 
>> The ASF voting rules are described at:
>>   http://www.apache.org/foundation/voting.html
>> 
>> A vote for accepting a new Apache Incubator podling is a majority vote
>> for which only Incubator PMC member votes are binding.
>> 
>> Votes from other people are also welcome as an indication of peoples
>> enthusiasm (or lack thereof).
>> 
>> Please do not use this VOTE thread for discussions.
>> If needed, start a new thread instead.
>> 
>> This vote will run for at least 72 hours. Please VOTE as follows
>> [] +1 Accept Crail into the Apache Incubator
>> [] +0 Abstain.
>> [] -1 Do not accept Crail into the Apache Incubator because ...
>> 
>> The proposal below is also on the wiki:
>> https://wiki.apache.org/incubator/CrailProposal
>> 
>> ===
>> 
>> Abstract
>> 
>> Crail is a storage platform for sharing performance critical data in
>> distributed data processing jobs at very high speed. Crail is built
>> entirely upon principles of user-level I/O and specifically targets data
>> center deployments with fast network and storage hardware (e.g., 100Gbps
>> RDMA, plenty of DRAM, NVMe flash, etc.) as well as new modes of operation
>> such resource disaggregation or serverless computing. Crail is written in
>> Java and integrates seamlessly with the Apache data processing ecosystem.
>> It can be used as a backbone to accelerate high-level data operations such
>> as shuffle or broadcast, or as a cache to store hot data that is queried
>> repeatedly, or as a storage platform for sharing inter-job data in complex
>> multi-job pipelines, etc.
>> 
>> Proposal
>> 
>> Crail enables Apache data processing frameworks to run efficiently in next
>> generation data centers using fast storage and network hardware in
>> combination with resource (e.g., DRAM, Flash) disaggregation.
>> 
>> Background
>> 
>> Crail started as a research project at the IBM Zurich Research Laboratory
>> around 2014 aiming to integrate high-speed I/O hardware effectively into
>> large scale data processing systems.
>> 
>> Rational
>> 
>> During the last decade, I/O hardware has undergone rapid performance
>> improvements, typically in the order of magnitudes. Modern day networking
>> and storage hardware can deliver 100+ Gbps (10+ GBps) bandwidth with a few
>> microseconds of access latencies. However, despite such progress in raw I/O
>> performance, effectively leveraging modern hardware in data processing
>> frameworks remains challenging. In most of the cases, upgrading to high-end
>> networking or storage hardware has very little effect on the performance of
>> analytics workloads. The problem comes from heavily layered software
>> imposing overheads such as deep call stacks, unnecessary data copies,
>> thread contention, etc. These problems have already been addressed at the
>> operating system level with new I/O APIs such as RDMA verbs, NVMe, etc.,
>> allowing applications to bypass software layers during I/O operations.
>> Distributed data processing frameworks on the other hand, are typically
>> implemented on legacy I/O interfaces such as such as sockets or block
>> storage. These interfaces have been shown to be insufficient to deliver the
>> full hardware performance. Yet, to the best of our knowledge, there are no
>> active and systematic efforts to integrate these new user level I/O APIs
>> into Apache software frameworks. This problem affects all end-users and
>> organizations that use Apache software. We expect them to see
>> unsatisfactory small performance gains when upgrading their networking and
>> storage hardware.
>> 
>> Crail solves this problem by providing an efficient storage platform built
>> upon user-level I/O, thus, bypassing layers such as JVM and OS during I/O
>> operations. Moreover, Crail directly leverages the specific hardware
>> features of RDMA and NVMe to provide a better integration with high-level
>> data operations in Apache compute frameworks. As a consequence, Crail
>> enables users to run larger, more complex queries against ever increasing
>> amounts of data at a speed largely determined by the deployed hardware.
>> Crail is generic solution that integrates well with the Apache ecosystem
>> including frameworks like Spark, Hadoop, Hive, etc.
>> 
>> Initial Goals
>> 
>> The initial goals to move Crail to the Apache Incubator is to broaden the
>> community, and foster contributions from developers to leverage Crail in
>> various data processing frameworks and workloads. Ultimately, the goal for
>> Crail is to become the de-facto standard platform for storing temporary
>> performance critical data in distributed data processing systems.
>> 
>> Current Status
>> 
>> The 

Re: [VOTE] Accept Crail into the Apache Incubator

[Patrick Stuedi]

Wow..great! In the name of the Crail team I want to thank Luciano,
Raphael and Julian for supporting us along the way and bringing the
project on for vote. I also want to thank everyone that voted for
Crail. We are looking forward to becoming an incubator project, and we
invite new contributors to join the project, there is plenty of
interesting stuff that can be done!

-Patrick

On Wed, Nov 1, 2017 at 2:42 PM, Luciano Resende  wrote:
> On Thu, Oct 26, 2017 at 8:31 AM, Luciano Resende 
> wrote:
>
>> Now that the discussion thread on the Crail proposal has ended, please
>> vote on accepting Crail into into the Apache Incubator.
>>
>> The ASF voting rules are described at:
>>http://www.apache.org/foundation/voting.html
>>
>> A vote for accepting a new Apache Incubator podling is a majority vote
>> for which only Incubator PMC member votes are binding.
>>
>> Votes from other people are also welcome as an indication of peoples
>> enthusiasm (or lack thereof).
>>
>> Please do not use this VOTE thread for discussions.
>> If needed, start a new thread instead.
>>
>> This vote will run for at least 72 hours. Please VOTE as follows
>> [] +1 Accept Crail into the Apache Incubator
>> [] +0 Abstain.
>> [] -1 Do not accept Crail into the Apache Incubator because ...
>>
>> The proposal below is also on the wiki:
>> https://wiki.apache.org/incubator/CrailProposal
>>
>> ===
>>
>> Abstract
>>
>> Crail is a storage platform for sharing performance critical data in
>> distributed data processing jobs at very high speed. Crail is built
>> entirely upon principles of user-level I/O and specifically targets data
>> center deployments with fast network and storage hardware (e.g., 100Gbps
>> RDMA, plenty of DRAM, NVMe flash, etc.) as well as new modes of operation
>> such resource disaggregation or serverless computing. Crail is written in
>> Java and integrates seamlessly with the Apache data processing ecosystem.
>> It can be used as a backbone to accelerate high-level data operations such
>> as shuffle or broadcast, or as a cache to store hot data that is queried
>> repeatedly, or as a storage platform for sharing inter-job data in complex
>> multi-job pipelines, etc.
>>
>> Proposal
>>
>> Crail enables Apache data processing frameworks to run efficiently in next
>> generation data centers using fast storage and network hardware in
>> combination with resource (e.g., DRAM, Flash) disaggregation.
>>
>> Background
>>
>> Crail started as a research project at the IBM Zurich Research Laboratory
>> around 2014 aiming to integrate high-speed I/O hardware effectively into
>> large scale data processing systems.
>>
>> Rational
>>
>> During the last decade, I/O hardware has undergone rapid performance
>> improvements, typically in the order of magnitudes. Modern day networking
>> and storage hardware can deliver 100+ Gbps (10+ GBps) bandwidth with a few
>> microseconds of access latencies. However, despite such progress in raw I/O
>> performance, effectively leveraging modern hardware in data processing
>> frameworks remains challenging. In most of the cases, upgrading to high-end
>> networking or storage hardware has very little effect on the performance of
>> analytics workloads. The problem comes from heavily layered software
>> imposing overheads such as deep call stacks, unnecessary data copies,
>> thread contention, etc. These problems have already been addressed at the
>> operating system level with new I/O APIs such as RDMA verbs, NVMe, etc.,
>> allowing applications to bypass software layers during I/O operations.
>> Distributed data processing frameworks on the other hand, are typically
>> implemented on legacy I/O interfaces such as such as sockets or block
>> storage. These interfaces have been shown to be insufficient to deliver the
>> full hardware performance. Yet, to the best of our knowledge, there are no
>> active and systematic efforts to integrate these new user level I/O APIs
>> into Apache software frameworks. This problem affects all end-users and
>> organizations that use Apache software. We expect them to see
>> unsatisfactory small performance gains when upgrading their networking and
>> storage hardware.
>>
>> Crail solves this problem by providing an efficient storage platform built
>> upon user-level I/O, thus, bypassing layers such as JVM and OS during I/O
>> operations. Moreover, Crail directly leverages the specific hardware
>> features of RDMA and NVMe to provide a better integration with high-level
>> data operations in Apache compute frameworks. As a consequence, Crail
>> enables users to run larger, more complex queries against ever increasing
>> amounts of data at a speed largely determined by the deployed hardware.
>> Crail is generic solution that integrates well with the Apache ecosystem
>> including frameworks like Spark, Hadoop, Hive, etc.
>>
>> Initial Goals
>>
>> The initial goals to move Crail to the Apache Incubator is to broaden the
>> 

Re: [VOTE] Accept Crail into the Apache Incubator

[Luciano Resende]

On Thu, Oct 26, 2017 at 8:31 AM, Luciano Resende 
wrote:

> Now that the discussion thread on the Crail proposal has ended, please
> vote on accepting Crail into into the Apache Incubator.
>
> The ASF voting rules are described at:
>http://www.apache.org/foundation/voting.html
>
> A vote for accepting a new Apache Incubator podling is a majority vote
> for which only Incubator PMC member votes are binding.
>
> Votes from other people are also welcome as an indication of peoples
> enthusiasm (or lack thereof).
>
> Please do not use this VOTE thread for discussions.
> If needed, start a new thread instead.
>
> This vote will run for at least 72 hours. Please VOTE as follows
> [] +1 Accept Crail into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Crail into the Apache Incubator because ...
>
> The proposal below is also on the wiki:
> https://wiki.apache.org/incubator/CrailProposal
>
> ===
>
> Abstract
>
> Crail is a storage platform for sharing performance critical data in
> distributed data processing jobs at very high speed. Crail is built
> entirely upon principles of user-level I/O and specifically targets data
> center deployments with fast network and storage hardware (e.g., 100Gbps
> RDMA, plenty of DRAM, NVMe flash, etc.) as well as new modes of operation
> such resource disaggregation or serverless computing. Crail is written in
> Java and integrates seamlessly with the Apache data processing ecosystem.
> It can be used as a backbone to accelerate high-level data operations such
> as shuffle or broadcast, or as a cache to store hot data that is queried
> repeatedly, or as a storage platform for sharing inter-job data in complex
> multi-job pipelines, etc.
>
> Proposal
>
> Crail enables Apache data processing frameworks to run efficiently in next
> generation data centers using fast storage and network hardware in
> combination with resource (e.g., DRAM, Flash) disaggregation.
>
> Background
>
> Crail started as a research project at the IBM Zurich Research Laboratory
> around 2014 aiming to integrate high-speed I/O hardware effectively into
> large scale data processing systems.
>
> Rational
>
> During the last decade, I/O hardware has undergone rapid performance
> improvements, typically in the order of magnitudes. Modern day networking
> and storage hardware can deliver 100+ Gbps (10+ GBps) bandwidth with a few
> microseconds of access latencies. However, despite such progress in raw I/O
> performance, effectively leveraging modern hardware in data processing
> frameworks remains challenging. In most of the cases, upgrading to high-end
> networking or storage hardware has very little effect on the performance of
> analytics workloads. The problem comes from heavily layered software
> imposing overheads such as deep call stacks, unnecessary data copies,
> thread contention, etc. These problems have already been addressed at the
> operating system level with new I/O APIs such as RDMA verbs, NVMe, etc.,
> allowing applications to bypass software layers during I/O operations.
> Distributed data processing frameworks on the other hand, are typically
> implemented on legacy I/O interfaces such as such as sockets or block
> storage. These interfaces have been shown to be insufficient to deliver the
> full hardware performance. Yet, to the best of our knowledge, there are no
> active and systematic efforts to integrate these new user level I/O APIs
> into Apache software frameworks. This problem affects all end-users and
> organizations that use Apache software. We expect them to see
> unsatisfactory small performance gains when upgrading their networking and
> storage hardware.
>
> Crail solves this problem by providing an efficient storage platform built
> upon user-level I/O, thus, bypassing layers such as JVM and OS during I/O
> operations. Moreover, Crail directly leverages the specific hardware
> features of RDMA and NVMe to provide a better integration with high-level
> data operations in Apache compute frameworks. As a consequence, Crail
> enables users to run larger, more complex queries against ever increasing
> amounts of data at a speed largely determined by the deployed hardware.
> Crail is generic solution that integrates well with the Apache ecosystem
> including frameworks like Spark, Hadoop, Hive, etc.
>
> Initial Goals
>
> The initial goals to move Crail to the Apache Incubator is to broaden the
> community, and foster contributions from developers to leverage Crail in
> various data processing frameworks and workloads. Ultimately, the goal for
> Crail is to become the de-facto standard platform for storing temporary
> performance critical data in distributed data processing systems.
>
> Current Status
>
> The initial code has been developed at the IBM Zurich Research Center and
> has recently been made available in GitHub under the Apache Software
> License 2.0. The Project currently has explicit support for Spark and
> Hadoop. Project 

Re: [VOTE] Apache Toree 0.2.0-incubating (RC1)

[Atri Sharma]

+1
-- Checked Headers
-- Checked License
-- Checked DISCLAIMER and Incubator policies

On Thu, Oct 26, 2017 at 9:37 PM, Luciano Resende  wrote:
> Please vote to approve the release of Apache Toree 0.2.0-incubating (RC1).
>
> The PPM vote thread:
> https://www.mail-archive.com/dev@toree.incubator.apache.org/msg01527.html
>
> And the result:
> https://www.mail-archive.com/dev@toree.incubator.apache.org/msg01539.html
>
> Tag: v0.2.0-incubating-rc1 (01cd97e9bad04878a8014016c154a50e2a00f21d)
>
> https://github.com/apache/incubator-toree/tree/v0.2.0-incubating-rc1
>
> All distribution packages, including signatures, digests, etc. can be found
> at:
>
> https://dist.apache.org/repos/dist/dev/incubator/toree/0.2.0-incubating-rc1/
>
> Staging artifacts can be found at:
>
> https://repository.apache.org/content/repositories/orgapachetoree-1007
>
> The vote is open for at least 72 hours and passes if a majority of at least
> 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Toree 0.2.0-incubating
> [ ] -1 Do not release this package because ...
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/



-- 
Regards,

Atri
l'apprenant

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Toree 0.2.0-incubating (RC1)

[Luciano Resende]

Here is my +1, any other volunteers to verify/vote for the release.

On Thu, Oct 26, 2017 at 9:07 AM, Luciano Resende 
wrote:

>
> Please vote to approve the release of Apache Toree 0.2.0-incubating (RC1).
>
> The PPM vote thread:
> https://www.mail-archive.com/dev@toree.incubator.apache.org/msg01527.html
>
> And the result:
> https://www.mail-archive.com/dev@toree.incubator.apache.org/msg01539.html
>
> Tag: v0.2.0-incubating-rc1 (01cd97e9bad04878a8014016c154a50e2a00f21d)
>
> https://github.com/apache/incubator-toree/tree/v0.2.0-incubating-rc1
>
> All distribution packages, including signatures, digests, etc. can be
> found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/toree/0.2.
> 0-incubating-rc1/
>
> Staging artifacts can be found at:
>
> https://repository.apache.org/content/repositories/orgapachetoree-1007
>
> The vote is open for at least 72 hours and passes if a majority of at
> least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Toree 0.2.0-incubating
> [ ] -1 Do not release this package because ...
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Daffodil Nov 2017 Podling Report

[John D. Ament]

Taylor

What is your wiki username?

On Nov 1, 2017 9:18 AM, "Taylor Wise"  wrote:

> Greetings,
>
>
> Could I receive write access to the wiki to add the Nov 2017 podling
> report for Daffodil?
>
>
> Thanks!
>
>
> -Taylor Wise
>

Daffodil Nov 2017 Podling Report

[Taylor Wise]

Greetings,


Could I receive write access to the wiki to add the Nov 2017 podling report for 
Daffodil?


Thanks!


-Taylor Wise

[RESULT][VOTE] Release Apache FreeMarker 2.3.27 (incubating)

[Woonsan Ko]

Hi all,

The vote for releasing Apache FreeMarker 2.3.27 (incubating) passed
with 3 binding "+1" votes, and no "0" or "-1" votes.

Binding votes:
  Jacopo Cappellato +1
  Jacques Le Roux +1
  Sergio Fernández +1

Non-binding votes:
  David E Jones +1 (on podling list only)
  Daniel Dekany +1 (on podling list only)
  Woonsan Ko +1
  Wen Tong +1

Apache FreeMarker (incubating) is a template engine, i.e. a generic
tool to generate text output based on templates. FreeMarker is
implemented in Java as a class library for programmers.

Thank you for the participation!

Regards,

Woonsan Ko
on behalf of Apache FreeMarker Podling Project Management Committee

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org