Re: [VOTE] MXNet to enter the Incubator

[Sebastian]

+1 (binding)

On 17.01.2017 07:18, Henry Saputra wrote:

+1 (binding)

Good luck!

On Mon, Jan 16, 2017 at 8:20 PM, Henri Yandell  wrote:


Hi Incubator folk,

   I would like to call a vote for accepting "MXNet" for incubation in the
Apache Incubator.

The full proposal is available at this wiki link:

https://wiki.apache.org/incubator/MXNetProposal?action=recall=19

I will reply to this email with a copy of the proposal.

MXNet already has a broad community, which I think is clear from the
interest from many contributors in being a part of the project at Apache.
There are four mentors signed up, along with 2 or 3 other Apache committers
looking to be involved in the project.

Please cast your vote:

  [ ] +1, bring MXNet into the Incubator
  [ ] -1, MXNet should not enter the Incubator, because...

 The vote will be open for at least 72 hours, and only votes from the
Incubator PMC are binding.

As the proposer, I consider my vote already cast in favour (and binding as
I'm a PMC member).

Thanks all,

Hen





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

Re: [VOTE] MXNet to enter the Incubator

[Henry Saputra]

+1 (binding)

Good luck!

On Mon, Jan 16, 2017 at 8:20 PM, Henri Yandell  wrote:

> Hi Incubator folk,
>
>I would like to call a vote for accepting "MXNet" for incubation in the
> Apache Incubator.
>
> The full proposal is available at this wiki link:
>
> https://wiki.apache.org/incubator/MXNetProposal?action=recall=19
>
> I will reply to this email with a copy of the proposal.
>
> MXNet already has a broad community, which I think is clear from the
> interest from many contributors in being a part of the project at Apache.
> There are four mentors signed up, along with 2 or 3 other Apache committers
> looking to be involved in the project.
>
> Please cast your vote:
>
>   [ ] +1, bring MXNet into the Incubator
>   [ ] -1, MXNet should not enter the Incubator, because...
>
>  The vote will be open for at least 72 hours, and only votes from the
> Incubator PMC are binding.
>
> As the proposer, I consider my vote already cast in favour (and binding as
> I'm a PMC member).
>
> Thanks all,
>
> Hen
>

Re: [VOTE] MXNet to enter the Incubator

[Henri Yandell]

Copy of the proposal text:
MXNet: Apache Incubator Proposal

Abstract

MXNet is a Flexible and Efficient Library for Deep Learning

Proposal

MXNet is an open-source deep learning framework that allows you to define,
train, and deploy deep neural networks on a wide array of devices, from
cloud infrastructure to mobile devices. It is highly scalable, allowing for
fast model training, and supports a flexible programming model and multiple
languages. MXNet allows you to mix symbolic and imperative programming
flavors to maximize both efficiency and productivity. MXNet is built on a
dynamic dependency scheduler that automatically parallelizes both symbolic
and imperative operations on the fly. A graph optimization layer on top of
that makes symbolic execution fast and memory efficient. The MXNet library
is portable and lightweight, and it scales to multiple GPUs and multiple
machines.

Background

Deep learning is a subset of Machine learning and refers to a class of
algorithms that use a hierarchical approach with non-linearities to
discover and learn representations within data. Deep Learning has recently
become very popular due to its applicability and advancement of domains
such as Computer Vision, Speech Recognition, Natural Language Understanding
and Recommender Systems. With pervasive and cost effective cloud computing,
large labeled datasets and continued algorithmic innovation, Deep Learning
has become the one of the most popular classes of algorithms for machine
learning practitioners in recent years.

Rational

The adoption of deep learning is quickly expanding from initial deep domain
experts rooted in academia to data scientists and developers working to
deploy intelligent services and products. Deep learning however has many
challenges. These include model training time (which can take days to
weeks), programmability (not everyone writes Python or C++ and like
symbolic programming) and balancing production readiness (support for
things like failover) with development flexibility (ability to program
different ways, support for new operators and model types) and speed of
execution (fast and scalable model training). Other frameworks excel on
some but not all of these aspects.

Initial Goals

MXNet is a fairly established project on GitHub
 with its first code contribution
in April 2015 and roughly 200 contributors. It is used by several large
companies and some of the top research institutions on the planet. Initial
goals would be the following:

   1. Move the existing codebase(s) to Apache
   2. Integrate with the Apache development process/sign CLAs
   3. Ensure all dependencies are compliant with Apache License version 2.0
   4. Incremental development and releases per Apache guidelines
   5. Establish engineering discipline and a predictable release cadence of
   high quality releases
   6. Expand the community beyond the current base of expert level users
   7. Improve usability and the overall developer/user experience
   8. Add additional functionality to address newer problem types and
   algorithms

Current Status

Meritocracy

The MXNet project already operates on meritocratic principles. Today, MXNet
has developers worldwide and has accepted multiple major patches from a
diverse set of contributors within both industry and academia. We would
like to follow ASF meritocratic principles to encourage more developers to
contribute in this project. We know that only active and committed
developers from a diverse set of backgrounds can make MXNet a successful
project. We are also improving the documentation and code to help new
developers get started quickly.

Community

Acceptance into the Apache foundation would bolster the growing user and
developer community around MXNet. That community includes around 200
contributors from academia and industry. The core developers of our project
are listed in our contributors below and are also represented by logos on
the mxnet.io site including Amazon, Baidu, Carnegie Mellon University,
Turi, Intel, NYU, Nvidia, MIT, Microsoft, TuSimple
, University of Alberta,
University of Washington and Wolfram.

Core Developers

(with GitHub  logins as an FYI)

   - Tianqi Chen (@tqchen)
   - Mu Li (@mli)
   - Junyuan Xie (@piiswrong)
   - Bing Xu (@antinucleon)
   - Chiyuan Zhang (@pluskid)
   - Minjie Wang (@jermainewang)
   - Naiyan Wang (@winstywang)
   - Yizhi Liu (@javelinjs)
   - Tong He (@hetong007)
   - Qiang Kou (@thirdwing)
   - Xingjian Shi (@sxjscience)
   - Yutian Li (@hotpxl)
   - Yuan Tang (@terrytangyuan)

Alignment

ASF is already the home of many distributed platforms, e.g., Hadoop, Spark
and Mahout, each of which targets a different application domain. MXNet,
being a distributed platform for large-scale deep learning, focuses on
another important domain for which there still lacks a scalable,
programmable, flexible and 

[VOTE] MXNet to enter the Incubator

[Henri Yandell]

Hi Incubator folk,

   I would like to call a vote for accepting "MXNet" for incubation in the
Apache Incubator.

The full proposal is available at this wiki link:

https://wiki.apache.org/incubator/MXNetProposal?action=recall=19

I will reply to this email with a copy of the proposal.

MXNet already has a broad community, which I think is clear from the
interest from many contributors in being a part of the project at Apache.
There are four mentors signed up, along with 2 or 3 other Apache committers
looking to be involved in the project.

Please cast your vote:

  [ ] +1, bring MXNet into the Incubator
  [ ] -1, MXNet should not enter the Incubator, because...

 The vote will be open for at least 72 hours, and only votes from the
Incubator PMC are binding.

As the proposer, I consider my vote already cast in favour (and binding as
I'm a PMC member).

Thanks all,

Hen

Re: [VOTE] Impala 2.8.0 release candidate 1

[Jim Apple]

Thank you for taking the time to check the artifact and vote.

> I didn't RAT check because I didn't have a rat.xml to use the script
> against and I wasn't sure how to create one.

bin/check-rat-report.py describes, on lines 28-30, how to run it,
including how to create rat.xml.

> Also the build uses a lot of bandwidth and takes quite some time. Might
> be worth pointing that out.

Good point. bin/bootstrap_build.sh takes 30-45 minutes on an ec2
c3xlarge instance, which voters can read about (in order to compare it
to their build machines) here:
https://aws.amazon.com/ec2/instance-types/

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

Re: [VOTE] Apache Toree (incubating) 0.1.0-rc4 as 0.1.0

[Luciano Resende]

It's ok, let's concentrate on getting the reviews done and 3 required
binding votes from IPMC members.

On Mon, Jan 16, 2017 at 10:57 AM, Chip Senkbeil 
wrote:

> Can't tell if my other mail got through. Do I need to open a new thread to
> indicate that the vote stays open for more than 72 hours? Or is it okay to
> make that statement here and keep this thread open?
>
> On Mon, Jan 16, 2017 at 11:19 AM Ian Dunlop  wrote:
>
> > Hello,
> >
> > I wonder if it would be better to say
> >
> > "The vote is open for *at least* 72 hours " (ie will not be closed until
> > at least 72 hours have passed)
> >
> > rather than
> >
> > "The vote is open for 72 hours " (ie will definitely be closed in 72
> hours
> > regardless of votes)
> >
> > The first version means that you have the option to keep the vote open
> > after the 72 hours have passed in case you don't have enough votes
> gathered.
> >
> > Cheers,
> >
> > Ian
> >
> >
> > On 16/01/17 15:34, Luciano Resende wrote:
> >
> > Bringing up my +1 from dev list.
> >
> > On Fri, Jan 13, 2017 at 2:43 PM, Chip Senkbeil 
> 
> > wrote:
> >
> >
> > Please vote on releasing the following candidate as Apache Toree
> > (incubating) version 0.1.0.
> >
> > A vote on this release has passed within the Toree PPMC.
> >
> > PPMC vote result thread:https://lists.apache.org/thread.html/
> 5589e9b729333b0d95ccea639fcacf
> > 03fdc3d9480aaeb8e80399ad35@
> > 
> >
> > PPMC vote thread:https://lists.apache.org/thread.html/
> 493874de453d9ccbdbc3aecc2f527d
> > ea6af82d657104732d726e07f9@
> > 
> >
> > The tag to be voted on is v0.1.0-rc4
> > (1d526954ecaba1d5dc0f40ec555dd598b2b11df7), located here:
> https://github.com/apache/incubator-toree/commit/
> > 1d526954ecaba1d5dc0f40ec555dd598b2b11df7
> >
> > All distribution packages, including signatures, digests, etc. can be
> found
> > at:https://dist.apache.org/repos/dist/dev/incubator/toree/0.1.0/rc4/
> >
> > Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/chipsenkbeil.asc
> >
> > The list of keys associated with Toree is available at:
> https://people.apache.org/keys/group/toree.asc
> >
> > Staging artifacts can be found at:https://repository.apache.
> org/content/repositories/orgapachetoree-1002/
> >
> > Please vote on releasing this package as Apache Toree 0.1.0-incubating!
> >
> > The vote is open for 72 hours - until Monday, January 16, at 22:43 UTC -
> > and passes if a majority of at least 3 +1 IPMC votes are cast.
> >
> > [ ] +1 Release this package as Apache Toree 0.1.0-incubating
> > [ ] -1 Do not release this package because ...
> >
> > To learn more about Apache Toree, please seehttp://toree.incubator.
> apache.org/
> >
> >
> >
> >
> >
>



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

[VOTE] Release of Apache Mnemonic-0.4.0-incubating [rc1]

[Gary]

Hello incubator PMCs,

The Apache Mnemonic community PPMCs and developers have voted and approved the 
proposal to release Apache Mnemonic 0.4.0 (incubating).

Apache Mnemonic is an advanced hybrid memory storage oriented library, it's 
proposed a non-volatile/durable Java object model and durable computing model 
that bring several advantages to significantly improve the performance of 
massive real-time data processing/analytic. developers are able to use this 
library to design their cache-less and SerDe-less high performance applications.

[VOTE] thread:
http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201612.mbox/%3C2cadfa42-9e64-e9cf-1a3e-bee220a89503%40apache.org%3E
http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201701.mbox/%3CCANLc_9KHFu4hawNSosjJADYQ8jtZTv5pThd5qBGBmbjAQOLBZw%40mail.gmail.com%3E
http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201701.mbox/%3CCALuGr6a5MM3Tsikt71W1%2BhGdbY9JpCB7z9Y8aaZb9NT0HkzDFg%40mail.gmail.com%3E
http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201701.mbox/%3CD49D5EAD.2C76A%25uma.gangumalla%40intel.com%3E

[VOTE RESULT] thread:
http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201701.mbox/%3C2c07ce2b-84b1-4751-d99a-5fe0de7ae24f%40apache.org%3E

We now kindly request the Incubator PMC members review and vote on this 
incubator release.

The Apache Mnemonic-0.4.0-incubating release candidate is now available with 
the following artifacts for a project vote:

The source tarball, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/incubator/mnemonic/0.4.0-incubating-rc1/src/

The tag to be voted upon is v0.4.0-incubating:
https://git-wip-us.apache.org/repos/asf?p=incubator-mnemonic.git;a=shortlog;h=refs/tags/v0.4.0-incubating

The release hash is 178035c68f1df26e4f3fcf9314bb6248c2ad3ac0:
https://git-wip-us.apache.org/repos/asf?p=incubator-mnemonic.git;a=commit;h=7799e7094545db9640269d14543bf28d7a7e0335

Release artifacts are signed with the following key:
https://dist.apache.org/repos/dist/dev/incubator/mnemonic/KEYS

KEYS file available:
https://dist.apache.org/repos/dist/dev/incubator/mnemonic/KEYS

For information about the contents of this release, see:
https://dist.apache.org/repos/dist/dev/incubator/mnemonic/0.4.0-incubating-rc1/CHANGES.txt

The vote will be open for ~72 hours.
Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, and test.  The
please vote:

[ ] +1 Release this package as apache-mnemonic-0.4.0-incubating
[ ] +0 no opinion
[ ] -1 Do not release this package because because...


Thanks,
Gary on behalf of the Apache Mnemonic (incubating) team




signature.asc
Description: OpenPGP digital signature

Re: [VOTE] Apache Toree (incubating) 0.1.0-rc4 as 0.1.0

[Chip Senkbeil]

Can't tell if my other mail got through. Do I need to open a new thread to
indicate that the vote stays open for more than 72 hours? Or is it okay to
make that statement here and keep this thread open?

On Mon, Jan 16, 2017 at 11:19 AM Ian Dunlop  wrote:

> Hello,
>
> I wonder if it would be better to say
>
> "The vote is open for *at least* 72 hours " (ie will not be closed until
> at least 72 hours have passed)
>
> rather than
>
> "The vote is open for 72 hours " (ie will definitely be closed in 72 hours
> regardless of votes)
>
> The first version means that you have the option to keep the vote open
> after the 72 hours have passed in case you don't have enough votes gathered.
>
> Cheers,
>
> Ian
>
>
> On 16/01/17 15:34, Luciano Resende wrote:
>
> Bringing up my +1 from dev list.
>
> On Fri, Jan 13, 2017 at 2:43 PM, Chip Senkbeil  
> 
> wrote:
>
>
> Please vote on releasing the following candidate as Apache Toree
> (incubating) version 0.1.0.
>
> A vote on this release has passed within the Toree PPMC.
>
> PPMC vote result 
> thread:https://lists.apache.org/thread.html/5589e9b729333b0d95ccea639fcacf
> 03fdc3d9480aaeb8e80399ad35@
> 
>
> PPMC vote 
> thread:https://lists.apache.org/thread.html/493874de453d9ccbdbc3aecc2f527d
> ea6af82d657104732d726e07f9@
> 
>
> The tag to be voted on is v0.1.0-rc4
> (1d526954ecaba1d5dc0f40ec555dd598b2b11df7), located 
> here:https://github.com/apache/incubator-toree/commit/
> 1d526954ecaba1d5dc0f40ec555dd598b2b11df7
>
> All distribution packages, including signatures, digests, etc. can be found
> at:https://dist.apache.org/repos/dist/dev/incubator/toree/0.1.0/rc4/
>
> Release artifacts are signed with the following 
> key:https://people.apache.org/keys/committer/chipsenkbeil.asc
>
> The list of keys associated with Toree is available 
> at:https://people.apache.org/keys/group/toree.asc
>
> Staging artifacts can be found 
> at:https://repository.apache.org/content/repositories/orgapachetoree-1002/
>
> Please vote on releasing this package as Apache Toree 0.1.0-incubating!
>
> The vote is open for 72 hours - until Monday, January 16, at 22:43 UTC -
> and passes if a majority of at least 3 +1 IPMC votes are cast.
>
> [ ] +1 Release this package as Apache Toree 0.1.0-incubating
> [ ] -1 Do not release this package because ...
>
> To learn more about Apache Toree, please seehttp://toree.incubator.apache.org/
>
>
>
>
>

Re: LDAP changes to support podlings

[Stian Soiland-Reyes]

Not sure what was the decision to be made here, but +1 to all suggestions.
All of PPMC as podling owners makes sense to me as long as private@podling
is notified.

Great work!



On 16 Jan 2017 6:05 pm, "Sam Ruby"  wrote:

> TL;DR: We need to decide, for each PPMC, who gets to update the PPMC list
> and where notifications to be sent on changes.
>
> ---
>
> Background: we have a variety of tools that need access to PPMC member
> lists, including but not limited to: gitbox, phonebook, ponymail, roller,
> sonar, subversion, and whimsy.
>
> The plan is to consolidate all of this to LDAP.  Previously, a number of
> 'auth groups' were migrated from the subversion puppet definition to LDAP.
> The plan is to do podlings next, and ultimately change the way PMCs are
> stored in LDAP.
>
> Currently the 'best' (as in machine readable) list of ppmc member
> information is in the subversion puppet definition - even for podlings that
> don't make use of subversion as this currently is the most expeditious way
> to get ppmc member lists to show up in the the phonebook application.
>
> The cleanest list of mentors can be found in podlings.xml.
>
> More complete, but less machine readable, and not always consistently
> maintained information can be found on the individual
> https://incubator.apache.org/projects/ pages.
>
> ---
> gitbox, phonebook, ponymail, roller, sonar, subversion
> Current status: for ppmcs that have lists in the subversion puppet
> definitions, those lists have been loaded into LDAP, and augmented with
> mentor information from podlings.xml.  A list of all current podlings can
> be found here, and those that have been loaded contain links to individual
> pages:
>
> https://whimsy.apache.org/roster/ppmc/
>
> These pages are currently read-only, and contain links to the project
> page, mailing lists, and prior published reports.
>
> ---
>
> Near future: what we need to resolve is who should be the 'owners' and who
> should be the 'members' for each PPMC.  These are LDAP terms, and they can
> be disjoint, overlapping, or even identical.
>
> The key point is that owners can change membership of the lists, and
> members are what gitbox, ponymail, roller, sonar, and subversion will use
> for access control.
>
> No matter what is decided, owners will be limited to adding and removing
> people who are already committers; adding new ids entirely will still
> require using the new account request web page.  Furthermore, all change
> will trigger notification to, at a minimum, root@.  Additionally
> notifying the individual affected, the private list for the podling, and or
> the private list for the incubator are possibilities.
>
> Given that these controls will be in place, allowing all members to also
> be owners should be safe.  Limiting owners to only mentors would also be a
> valid choice.  This need not be the same choice for all PPMCs, but it
> probably would make life (and tooling) easier if it were.
>
> Once this decision is made, the whimsy roster tool will be updated to
> allow owners to update lists, and those owners will be asked to do so. At
> that point, the subversion access lists in puppet will be converted over to
> LDAP, and the infra team will stop accepting JIRA requests to maintain
> these lists.
>
> ---
>
> Not so distant future: the tools mentioned above will all be updated to
> use the common LDAP definition for podling membership.  As an example, the
> phonebook application will include all podlings, with data automatically
> updated within hours of a change.
>
> The whimsy roster tool currently contains links to mailing lists and
> posted board reports.  It could be updated to include links to other tools
> ranging from subscribing and unsubscribing to mailing lists to static sonar
> analysis.
>
> New tools could be built using this data: for example, all of the data
> needed to draft board resolutions related to graduation could be gathered
> from LDAP and podlings.xml.
>
> ---
>
> Further in the future: PMC definitions will be changed to match the way
> PPMC definitions are done.  At the present time, only PMC chairs can update
> PMC member and committer lists -- even for PMCs to which they don't
> belong.  Other PMC members who aren't PMC chairs can't update their own
> lists.
>
> - Sam Ruby
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

LDAP changes to support podlings

[Sam Ruby]

TL;DR: We need to decide, for each PPMC, who gets to update the PPMC 
list and where notifications to be sent on changes.


---

Background: we have a variety of tools that need access to PPMC member 
lists, including but not limited to: gitbox, phonebook, ponymail, 
roller, sonar, subversion, and whimsy.


The plan is to consolidate all of this to LDAP.  Previously, a number of 
'auth groups' were migrated from the subversion puppet definition to 
LDAP.  The plan is to do podlings next, and ultimately change the way 
PMCs are stored in LDAP.


Currently the 'best' (as in machine readable) list of ppmc member 
information is in the subversion puppet definition - even for podlings 
that don't make use of subversion as this currently is the most 
expeditious way to get ppmc member lists to show up in the the phonebook 
application.


The cleanest list of mentors can be found in podlings.xml.

More complete, but less machine readable, and not always consistently 
maintained information can be found on the individual 
https://incubator.apache.org/projects/ pages.


---
gitbox, phonebook, ponymail, roller, sonar, subversion
Current status: for ppmcs that have lists in the subversion puppet 
definitions, those lists have been loaded into LDAP, and augmented with 
mentor information from podlings.xml.  A list of all current podlings 
can be found here, and those that have been loaded contain links to 
individual pages:


https://whimsy.apache.org/roster/ppmc/

These pages are currently read-only, and contain links to the project 
page, mailing lists, and prior published reports.


---

Near future: what we need to resolve is who should be the 'owners' and 
who should be the 'members' for each PPMC.  These are LDAP terms, and 
they can be disjoint, overlapping, or even identical.


The key point is that owners can change membership of the lists, and 
members are what gitbox, ponymail, roller, sonar, and subversion will 
use for access control.


No matter what is decided, owners will be limited to adding and removing 
people who are already committers; adding new ids entirely will still 
require using the new account request web page.  Furthermore, all change 
will trigger notification to, at a minimum, root@.  Additionally 
notifying the individual affected, the private list for the podling, and 
or the private list for the incubator are possibilities.


Given that these controls will be in place, allowing all members to also 
be owners should be safe.  Limiting owners to only mentors would also be 
a valid choice.  This need not be the same choice for all PPMCs, but it 
probably would make life (and tooling) easier if it were.


Once this decision is made, the whimsy roster tool will be updated to 
allow owners to update lists, and those owners will be asked to do so. 
At that point, the subversion access lists in puppet will be converted 
over to LDAP, and the infra team will stop accepting JIRA requests to 
maintain these lists.


---

Not so distant future: the tools mentioned above will all be updated to 
use the common LDAP definition for podling membership.  As an example, 
the phonebook application will include all podlings, with data 
automatically updated within hours of a change.


The whimsy roster tool currently contains links to mailing lists and 
posted board reports.  It could be updated to include links to other 
tools ranging from subscribing and unsubscribing to mailing lists to 
static sonar analysis.


New tools could be built using this data: for example, all of the data 
needed to draft board resolutions related to graduation could be 
gathered from LDAP and podlings.xml.


---

Further in the future: PMC definitions will be changed to match the way 
PPMC definitions are done.  At the present time, only PMC chairs can 
update PMC member and committer lists -- even for PMCs to which they 
don't belong.  Other PMC members who aren't PMC chairs can't update 
their own lists.


- Sam Ruby

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

Re: [VOTE] Apache Toree (incubating) 0.1.0-rc4 as 0.1.0

[Ian Dunlop]

Hello,

I wonder if it would be better to say

"The vote is open for _at least_ 72 hours " (ie will not be closed until
at least 72 hours have passed)

rather than

"The vote is open for 72 hours " (ie will definitely be closed in 72
hours regardless of votes)

The first version means that you have the option to keep the vote open
after the 72 hours have passed in case you don't have enough votes gathered.


Cheers,

Ian

On 16/01/17 15:34, Luciano Resende wrote:
> Bringing up my +1 from dev list.
>
> On Fri, Jan 13, 2017 at 2:43 PM, Chip Senkbeil 
> wrote:
>
>> Please vote on releasing the following candidate as Apache Toree
>> (incubating) version 0.1.0.
>>
>> A vote on this release has passed within the Toree PPMC.
>>
>> PPMC vote result thread:
>> https://lists.apache.org/thread.html/5589e9b729333b0d95ccea639fcacf
>> 03fdc3d9480aaeb8e80399ad35@
>> 
>>
>> PPMC vote thread:
>> https://lists.apache.org/thread.html/493874de453d9ccbdbc3aecc2f527d
>> ea6af82d657104732d726e07f9@
>> 
>>
>> The tag to be voted on is v0.1.0-rc4
>> (1d526954ecaba1d5dc0f40ec555dd598b2b11df7), located here:
>> https://github.com/apache/incubator-toree/commit/
>> 1d526954ecaba1d5dc0f40ec555dd598b2b11df7
>>
>> All distribution packages, including signatures, digests, etc. can be found
>> at:
>> https://dist.apache.org/repos/dist/dev/incubator/toree/0.1.0/rc4/
>>
>> Release artifacts are signed with the following key:
>> https://people.apache.org/keys/committer/chipsenkbeil.asc
>>
>> The list of keys associated with Toree is available at:
>> https://people.apache.org/keys/group/toree.asc
>>
>> Staging artifacts can be found at:
>> https://repository.apache.org/content/repositories/orgapachetoree-1002/
>>
>> Please vote on releasing this package as Apache Toree 0.1.0-incubating!
>>
>> The vote is open for 72 hours - until Monday, January 16, at 22:43 UTC -
>> and passes if a majority of at least 3 +1 IPMC votes are cast.
>>
>> [ ] +1 Release this package as Apache Toree 0.1.0-incubating
>> [ ] -1 Do not release this package because ...
>>
>> To learn more about Apache Toree, please see
>> http://toree.incubator.apache.org/
>>
>
>



signature.asc
Description: OpenPGP digital signature

Re: [VOTE] Apache Toree (incubating) 0.1.0-rc4 as 0.1.0

[Luciano Resende]

Bringing up my +1 from dev list.

On Fri, Jan 13, 2017 at 2:43 PM, Chip Senkbeil 
wrote:

> Please vote on releasing the following candidate as Apache Toree
> (incubating) version 0.1.0.
>
> A vote on this release has passed within the Toree PPMC.
>
> PPMC vote result thread:
> https://lists.apache.org/thread.html/5589e9b729333b0d95ccea639fcacf
> 03fdc3d9480aaeb8e80399ad35@
> 
>
> PPMC vote thread:
> https://lists.apache.org/thread.html/493874de453d9ccbdbc3aecc2f527d
> ea6af82d657104732d726e07f9@
> 
>
> The tag to be voted on is v0.1.0-rc4
> (1d526954ecaba1d5dc0f40ec555dd598b2b11df7), located here:
> https://github.com/apache/incubator-toree/commit/
> 1d526954ecaba1d5dc0f40ec555dd598b2b11df7
>
> All distribution packages, including signatures, digests, etc. can be found
> at:
> https://dist.apache.org/repos/dist/dev/incubator/toree/0.1.0/rc4/
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/chipsenkbeil.asc
>
> The list of keys associated with Toree is available at:
> https://people.apache.org/keys/group/toree.asc
>
> Staging artifacts can be found at:
> https://repository.apache.org/content/repositories/orgapachetoree-1002/
>
> Please vote on releasing this package as Apache Toree 0.1.0-incubating!
>
> The vote is open for 72 hours - until Monday, January 16, at 22:43 UTC -
> and passes if a majority of at least 3 +1 IPMC votes are cast.
>
> [ ] +1 Release this package as Apache Toree 0.1.0-incubating
> [ ] -1 Do not release this package because ...
>
> To learn more about Apache Toree, please see
> http://toree.incubator.apache.org/
>



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

Re: [VOTE] Impala 2.8.0 release candidate 1

[Ian Dunlop]

Hello,

+1

I checked:

MD5 sum

SHA1 sum

build

I didn't RAT check because I didn't have a rat.xml to use the script
against and I wasn't sure how to create one.

Note. Build passed but complained slightly:

cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for
C/ObjC but not for C++
sasl/saslwrapper.cpp: In member function ‘bool
saslwrapper::ClientImpl::init()’:
sasl/saslwrapper.cpp:89:9: warning: unused variable ‘cbIndex’
[-Wunused-variable]
 int cbIndex = 0;
 ^
sasl/saslwrapper.cpp: In member function ‘void
saslwrapper::ClientImpl::interact(sasl_interact_t*)’:
sasl/saslwrapper.cpp:319:11: warning: unused variable ‘input’
[-Wunused-variable]
 char* input;
   ^
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for
C/ObjC but not for C++


Also the build uses a lot of bandwidth and takes quite some time. Might
be worth pointing that out.

Cheers,

Ian


On 12/01/17 15:57, Jim Apple wrote:
> Impala 2.8.0 release candidate 1 has passed a PPMC vote; this email is
> a call for an IPMC vote.
>
> The PPMC vote thread is:
>
> https://lists.apache.org/thread.html/f873d0f82f0619d7d9a18440a74ea2961e63e4db0c5216a9d08b6517@%3Cdev.impala.apache.org%3E
>
> http://mail-archives.apache.org/mod_mbox/impala-dev/201701.mbox/%3CCAC-pSX2TG7z6L8qWP9NjmonJfmUfTD_xxHs-YH44C--3aaPFUQ%40mail.gmail.com%3E
>
> The vote result thread is:
>
> https://lists.apache.org/thread.html/856ea124d95b58f251f2737955bd70b1160d29d9c3dd960e1bb90cea@%3Cdev.impala.apache.org%3E
>
>  The artifacts for testing are at
> .
> That is git tag 2.8.0-rc1, tree hash
> cc8de358d5c64778d171ad47aa6b513d437ac4b0, visible at
> .
>
> The KEYS are at 
> .
>
> To run RAT, follow the instructions in bin/check-rat-report.py. To
> build, follow the instructions in bin/bootstrap_build.sh.
>
> One of the binding votes from the PPMC was Tom White, who is one of
> our mentors and an IPMC member.
>
> This vote will be open for at least 72 hours, or until the necessary
> number of votes (3 +1) is reached.
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>




signature.asc
Description: OpenPGP digital signature