+1 (binding)
On Fri, May 15, 2020 at 5:40 PM Ryan Blue wrote:
> Hi everyone,
>
> With the support of our mentors (as well as helpful ASF members), the
> Apache Iceberg community has voted to graduate to a top-level project.
>
> I propose a vote to recommend graduation for the Iceberg community t
+1. That seems like the best course of action IMHO.
On Wed, Oct 23, 2019 at 12:54 PM Flavio Junqueira wrote:
> +1
>
> -Flavio
>
> > On 23 Oct 2019, at 21:08, Terence Yim wrote:
> >
> > +1 on this
> >
> > On Wed, Oct 23, 2019 at 11:36 Dave Fisher wrote:
> >
> >> +1. That’s a good idea.
> >>
> >
+1 (binding).
Successfully downloaded, verified license, verified checksum, verified
signature, built from source, and ran unit tests.
Minor nit (ok to fix in next release IMHO): Copyright in NOTICE for Iceberg
should read 2017-2019
On Tue, Oct 22, 2019 at 3:21 PM Ryan Blue wrote:
> Hi everyo
Transferring my +1 from the dev list vote.
FYI, the correct pointer the the PPMC vote is here:
https://s.apache.org/8q5z
Thanks,
James
On Mon, May 6, 2019 at 7:43 AM James Taylor wrote:
> Thanks, Justin. I've fixed the roster for Omid.
>
> On Sun, May 5, 2019 at 3:47 PM
Thanks, Justin. I've fixed the roster for Omid.
On Sun, May 5, 2019 at 3:47 PM Justin Mclean
wrote:
> Hi,
>
>
> > 4 binding (IPMC member) +1 votes
>
> I only count 2 IPMC votes (from your mentors) have I miscounted?
>
> Can you also please fix up your roster [1] as it currently shows no PPMC
> m
Transferring my +1 from the dev vote.
On Sat, Nov 17, 2018 at 11:45 PM Ohad Shacham
wrote:
> Hi,
>
>
> The Apache Omid community has voted on and approved a proposal
> to release Apache Omid 1.0.0-incubating.
>
> PPMC Vote Call:
> http://mail-archives.apache.org/mod_mbox/omid-dev/201811.mbox/%3c
+1 (binding)
On Tue, Nov 13, 2018 at 4:15 PM Willem Jiang wrote:
> +1 (binding)
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Wed, Nov 14, 2018 at 1:07 AM Ryan Blue wrote:
> >
> > The discuss thread seems to have reached consensus, so I propose
> accepting
> > the Iceberg p
Hi All,
The Apache Tephra team is excited to announce the latest release of Apache
Tephra-0.15.0-incubating. This is the eighth release of Apache Tephra.
Apache Tephra is a transaction engine for distributed data stores like
Apache HBase. It provides ACID semantics for concurrent data operations
The vote is now closed and passes with 3 +1s and no +0 or -1s.
Thanks to those who voted.
James
On Tue, Sep 4, 2018 at 7:36 AM James Taylor wrote:
> +1 (binding)
>
> Built from scratch
> Successfully ran all unit tests
>
> On Tue, Sep 4, 2018 at 12:55 AM Justin Mclean
+1 (binding)
Built from scratch
Successfully ran all unit tests
On Tue, Sep 4, 2018 at 12:55 AM Justin Mclean
wrote:
> Hi,
>
> +1 (binding)
>
> I checked:
> - incubating in name
> - signatures and hashes good
> - LICENSE and NOTICE good (binary NOTICE year needs updating)
> - No unexpected bina
+1 (binding)
On Sun, Aug 26, 2018 at 8:41 PM Greg Trasuk wrote:
> +1 Accept Zipkin (binding).
>
> Greg Trasuk.
>
> > On Aug 26, 2018, at 11:14 PM, Mick Semb Wever wrote:
> >
> > After a brief discussion¹ I would like to call a VOTE to accept Zipkin
> into the Apache Incubator.
> > The full prop
+1
On Thu, Aug 23, 2018 at 3:11 AM wrote:
> Very excited about the proposal and looking forward to the Apache journey.
>
> Bas van Beek
>
> On 2018/08/17 09:29:47, Adrian Cole wrote:
> > I would like to propose Zipkin as an Apache Incubator project.>
> >
> > The text of the proposal can be foun
Hi all,
This is a call for a vote on releasing Apache Tephra 0.15.0-incubating,
release candidate 1. This is the eighth release of Tephra. The Tephra dev
community has voted on and approved a proposal to release Tephra
0.15.0-incubating, release candidate 1.
PPMC Vote Call: https://s.apache.org/6
The vote is now closed and passes with 7 +1 votes and no +0 or -1 votes.
Thanks to everyone who voted.
James
On Thu, May 24, 2018 at 4:03 PM, James Taylor
wrote:
> +1 (transferred from my dev vote)
>
> On Thu, May 24, 2018 at 6:49 AM, larry mccay wrote:
>
>> * built f
ntain LICENSE and NOTICE files. I'm not sure how this
> > happened, since these files are typically added by default when projects
> > use the ASF parent pom.
> >
> > Billie
> >
> > On 5/21/18 6:51 PM, James Taylor wrote:
> >
> > > Hi all,
> > &
Hi all,
This is a call for a vote on releasing Apache Tephra 0.14.0-incubating,
release candidate 1. This is the seventh release of Tephra. The Tephra dev
community has voted on and approved a proposal to release Tephra
0.14.0-incubating, release candidate 1.
PPMC Vote Call: https://s.apache.org/
+1 (transferring my vote over from dev list vote)
On Mon, May 21, 2018 at 12:39 PM, Ohad Shacham
wrote:
> Hi,
>
>
> The Apache Omid community has voted on and approved a proposal
> to release Apache Omid 0.9.0.0-incubating.
>
> PPMC Vote Call:http://mail-archives.apache.org/mod_mbox/omid-dev/
>
@Justin - thanks for taking the time to review. Really appreciate it. Looks
like there's some confusion, though. Prior to starting this vote, you
approved the change on the JIRA here[1], but now you've -1'ed the release.
At this point, we're trying to get clarification on OMID-44 so that when we
go
Forwarding my +1 from the dev list.
James
On Thu, Mar 22, 2018 at 8:31 AM Henk P. Penning wrote:
> On Thu, 22 Mar 2018, Ohad Shacham wrote:
>
> > Date: Thu, 22 Mar 2018 13:29:55 +0100
> > From: Ohad Shacham
> > To: general@incubator.apache.org
> > Subject: [VOTE] Release Apache Omid 0.9.0.
+1 (binding)
On Thu, Feb 22, 2018 at 2:55 PM, Andrew Purtell wrote:
> +1 (binding)
>
>
> On Thu, Feb 22, 2018 at 11:03 AM, Julian Hyde wrote:
>
> > Hi all,
> >
> > After some discussion on the Druid proposal[1], I'd like to
> > start a vote on accepting Druid into the Apache Incubator,
> > per
John - there appears to be some confusion. Would you mind clearing up
whether you voted or not? Sorry for bugging you.
Thanks,
James
On Thu, Sep 21, 2017 at 1:30 PM, James Taylor
wrote:
> I thought John already changed his vote to +1 based on this comment, no?
>
> > On Wed, Sep 2
I thought John already changed his vote to +1 based on this comment, no?
> On Wed, Sep 20, 2017 at 7:56 PM, John D. Ament
> > wrote:
> >
> >> I'm fine with giving a +1 assuming the NOTICE issue is fixed for next
> >> release. Please feel free to ping me if you want a review of the NOTICE
> >> co
John - thanks for the review. If things look acceptable now, would you be
willing to cast a vote?
Anyone else?
Thanks,
James
On Wed, Sep 20, 2017 at 11:58 AM Gokul Gunasekaran wrote:
> Thanks, John! Is there anything else that we can do to address
> concerns/issues regarding the release candid
+1 (binding)
On Tue, Sep 19, 2017 at 1:45 PM, Luke Han wrote:
> +1 (binding)
>
>
> Best Regards!
> -
>
> Luke Han
>
> On Tue, Sep 19, 2017 at 11:58 AM, Debo Dutta (dedutta)
> wrote:
>
> > +1
> >
> > Sent from my iPhone
> >
> > > On Sep 19, 2017, at 11:58 AM, Johnu George wr
+1. Transferring my vote over from the dev list vote.
On Mon, Sep 18, 2017 at 10:13 AM, Andreas Neumann wrote:
> Hi all,
>
> This is a call for a vote on releasing Apache Tephra 0.13.0-incubating,
> release candidate 2. This is the sixth release of Tephra.
>
> The Apache Tephra community has vot
+1. The RC passes all Phoenix unit tests.
On Fri, May 26, 2017 at 3:22 PM, Alan Gates wrote:
> Forwarding my +1 from the dev list.
>
> Alan.
>
> On Fri, May 26, 2017 at 2:12 PM, Gokul Gunasekaran
> wrote:
>
> > Hi all,
> >
> > This is a call for a vote on releasing Apache Tephra 0.12.0-incubati
Forwarding my +1 from dev list too.
On Sat, Mar 11, 2017 at 8:53 AM Alan Gates wrote:
> Forwarding my +1 from the dev list.
>
> Alan.
>
> > On Mar 10, 2017, at 5:18 PM, Gokul Gunasekaran wrote:
> >
> > Hi all,
> >
> > This is a call for a vote on releasing Apache Tephra 0.11.0-incubating,
> > r
ough by marking TEPHRA-223 as a known
> issue. We can do a 0.11.1 release immediately after fixing TEPHRA-223.
>
> Thanks,
> Poorna.
>
>
>
> On Mon, Feb 20, 2017 at 2:37 PM, James Taylor
> wrote:
>
> > Looks like a serious issue was found with TEPHRA-223, so swi
Looks like a serious issue was found with TEPHRA-223, so switching my vote
to -1. Hopefully we can get a quick fix with a new RC very soon.
James
On Fri, Feb 17, 2017 at 12:12 PM, Alan Gates wrote:
> Forwarding my +1 from the dev list.
>
> Alan.
>
> > On Feb 17, 2017,
Transferring my +1 from the dev list vote over here.
On Fri, Feb 17, 2017 at 11:40 AM, Gokul Gunasekaran
wrote:
> Hi all,
>
> This is a call for a vote on releasing Apache Tephra 0.11.0-incubating,
> release candidate 1. This is the fourth release of Tephra.
>
> Apache Tephra community has voted
+1. Verified all Phoenix unit tests pass with the proposed release.
James
On Mon, Dec 12, 2016 at 4:24 PM, Alan Gates wrote:
> Forwarding my +1 from the dev list.
>
> Alan.
>
> > On Dec 12, 2016, at 15:46, Gokul Gunasekaran wrote:
> >
> > Hi all,
> >
> > This is a call for a vote on releas
+1 (binding)
On Tue, Dec 6, 2016 at 7:38 AM, Tom Barber wrote:
> +1
>
> On Tue, Dec 6, 2016 at 3:37 PM, Stephan Ewen wrote:
>
> > +1 (binding)
> >
> >
> >
> > On Tue, Dec 6, 2016 at 1:27 PM, Sandeep Deshmukh <
> sand...@datatorrent.com>
> > wrote:
> >
> > > +1 (non-binding)
> > >
> > > Regards,
Transferring my +1 from dev vote here.
On Thu, Sep 15, 2016 at 10:44 PM, Poorna Chandra wrote:
> Hi all,
>
> This is a call for a vote on releasing Apache Tephra 0.9.0-incubating,
> release candidate 1. This is the second release of Tephra.
>
> Apache Tephra community has voted and approved the
+1 (binding)
On Thursday, June 2, 2016, Andrew Purtell wrote:
> +1 (binding)
>
> On Thu, Jun 2, 2016 at 3:06 PM, Henry Saputra >
> wrote:
>
> > Hi All,
> >
> > Following the DISCUSS thread about Apache Twill graduating as TLP, I
> would
> > like to send VOTE request thread.
> >
> > All the +1 b
+1 (binding)
On Tue, May 24, 2016 at 7:48 AM, Billie Rinaldi wrote:
> +1 (binding)
>
> On Tue, May 24, 2016 at 7:56 AM, Daniel Gruno
> wrote:
> > Since it seems the discussion has died down, I am now calling a vote on
> > accepting Pony Mail into the Incubator. Sorry in advance for potato.
> >
https://predictionio.incubator.apache.org/docs/
> >
> > JIRA instance
> >
> > PredictionIO currently uses the GitHub issue tracking system associated
> > with its repository:
> https://github.com/PredictionIO/PredictionIO/issues
> > .
> > We w
licenses that we would need to include?
> I realize this may sound like nit-picking. But it is an important aspect
> of the incubation time.
>
> I have to vote -1 .
>
> -- Lars
>
> From: James Taylor
> To: "general@incubator.apache.org"
> Sent: Frida
, that can be a networking problem on Macs unless using a
> very recent version of the JDK, or any number of reasons really
> (minicluster is as complex as it sounds). Anyway, perhaps posting the
> complete test output from surefire to the project JIRA is in order?
>
>
> > On May
Thanks for the testing, John. It builds on my MacBook Pro:
OS X Version 10.11.4
java version 1.7.0_80
What's your system look like?
On Sat, May 21, 2016 at 6:53 AM, John D. Ament
wrote:
> Hi,
>
> I'm +0 for right now unless there's a way to make the code build and test
> on a mac and I
Thanks for the reviews. There are a few files with a package
of co.cask.tephra in order to maintain backward compatibility with pre
Apache-based releases. These will be removed in a follow on release.
James
On Fri, May 20, 2016 at 10:55 PM, Justin Mclean
wrote:
> Hi,
>
> > The source code s
+1. Transferring my vote over from the previous vote thread.
On Fri, May 20, 2016 at 3:47 PM, Poorna Chandra wrote:
> Hi all,
>
> This is a call for a vote on releasing Apache Tephra 0.8.0-incubating,
> release candidate 1. This
> is the first release of Tephra.
>
> Apache Tephra community has v
+1 (binding)
On Sat, May 14, 2016 at 9:31 AM, Roman Shaposhnik
wrote:
> On Fri, May 13, 2016 at 11:22 AM, Billie Rinaldi
> wrote:
> > Since discussion has died down, I would like to call a VOTE on accepting
> > Fluo into the Apache Incubator.
> >
> > Proposal: http://wiki.apache.org/incubator/F
Me too - my bad. So sorry. I'm embarrassed to admit I can't find an email
for it.
On Tuesday, April 12, 2016, Henry Saputra wrote:
> No need to be curious too much, mea culpa from me for missing signing off
> the report :)
>
> I had the impression I did sign off the report for Mnemonic, sincerel
ies that are not Apache projects are
> >all Apache licenses or other compatible Licenses:
> >
> >
> >Maven & Maven plugins (http://maven.apache.org/) [Apache 2.0]
> >JDK7 or OpenJDK 7 (http://java.com/) [Oracle or Openjdk JDK License]
> >Google Guava v11.0.2 (https://gith
on Apache Zookeeper and Curator projects in order to
> > > > coordinate the (re)connection of transaction managers (acting as
> > > > clients) to the conflict resolution component for transactions
> (server
> > > > side.) They’re also used in order to c
e incubation
> > process
> > Cask Data will transfer the trademark to Apache Foundation.
> >
> > = External Dependencies =
> >
> > The dependencies all have Apache-compatible licenses:
> > * dropwizard metrics (Apache 2.0)
> > * fastutil (Apache
+1 (binding)
On Tue, Mar 1, 2016 at 4:53 PM, Andrew Purtell wrote:
> Greetings,
>
> The discussion of the Gearpump proposal has concluded. Please vote to
> accept Gearpump into the Apache Incubator. I will leave this vote open for
> at least the next 72 hours and will aim to close it Monday the
t onto ASF
> > > infrastructure and in turn made available under the Apache License,
> > > version 2.0.
> > >
> > > === External Dependencies ===
> > > The required external dependencies are all Apache licenses or other
> > > compatible Lice
+1
On Fri, Feb 26, 2016 at 8:47 AM, Arvind Prabhakar wrote:
> +1 (binding)
>
> Regards,
> Arvind
>
> On Wed, Feb 24, 2016 at 9:01 AM, Katherine Marsden
> wrote:
>
> > The Quarks proposal has been discussed on the incubator list. The
> > discussion thread is at:
> >
> >
> http://mail-archives.a
+1 (binding)
On Thu, Jan 28, 2016 at 6:28 AM, Jean-Baptiste Onofré
wrote:
> Hi,
>
> the Beam proposal (initially Dataflow) was proposed last week.
>
> The complete discussion thread is available here:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-general/201601.mbox/%3CCA%2B%3DKJmvj4w
+1 (binding). Interesting proposal and I love the name.
On Wed, Jan 20, 2016 at 12:58 PM, Seetharam Venkatesh <
venkat...@innerzeal.com> wrote:
> +1 (binding).
>
> Thanks!
>
> On Wed, Jan 20, 2016 at 8:49 AM Julian Hyde wrote:
>
> > +1 (binding)
> >
> > Julian
> >
> > > On Jan 19, 2016, at 10:43
My apologies, Marvin, and thanks for clarifying the procedure. I'll follow
up on the private list.
James
On Sat, Dec 12, 2015 at 11:33 AM, Marvin Humphrey
wrote:
> On Sat, Dec 12, 2015 at 11:04 AM, James Taylor
> wrote:
> > Hello,
> > I'm the PMC Chair for Apa
Hello,
I'm the PMC Chair for Apache Phoenix and a PMC member of Apache Calcite,
both top level project and both of which I went through the incubation
process. Recently several projects interested in going through incubation
approached me to be a mentor, hence my interest in joining - so that I can
gt;
> -Jake
>
> [1]: http://incubator.apache.org/guides/graduation.html#unincubate
>
>
> On Wed, May 28, 2014 at 1:41 PM, James Taylor >wrote:
>
> > FYI, Phoenix has graduated as reported last month.
> > Thanks,
> > James
> >
> > On We
FYI, Phoenix has graduated as reported last month.
Thanks,
James
On Wednesday, May 28, 2014, Marvin wrote:
>
>
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC.
> It is an initial reminder to give you plenty of time to prepare your
> quarterl
Hello everyone,
I'm pleased to report that this VOTE has passed with the 9 +1 votes (7
binding):
+1
Eli Levine
Steven Noels*
Michael Stack*
Andrew Purtell*
Roman Shaposhnik*
Lars Hofhansl*
Devaraj Das*
Enis Söztutar*
James Taylor
* - indicates IPMC
I will add the resolution to the board a
+1
On Fri, May 2, 2014 at 5:00 PM, Enis Söztutar wrote:
> +1 (binding)
>
> Enis
>
>
> On Fri, May 2, 2014 at 4:51 PM, Devaraj Das wrote:
>
> > +1
> >
> > On Wed, Apr 30, 2014 at 10:44 PM, James Taylor
> > wrote:
> > > Hi everyone,
> &
Hi everyone,
The Apache Phoenix podling has has discussed and voted to graduate from the
incubator with 22 +1 votes, 5 of which were IPMC vote [1]. We've made three
releases, increased our contributor and committer list [2], and have an
active, thriving community.
Please VOTE below on the graduat
Hello everyone,
The Apache Phoenix team is pleased to announce the release of version
4.0.0-incubating from the Apache Incubator. Phoenix is a SQL query engine
for Apache HBase, a NoSQL data store. It is accessed as a JDBC driver and
enables querying and managing HBase tables using SQL.
This is the
Hello everyone,
The Apache Phoenix team is pleased to announce the release of version
3.0.0-incubating from the Apache Incubator. Phoenix is a SQL query engine
for Apache HBase, a NoSQL data store. It is accessed as a JDBC driver and
enables querying and managing HBase tables using SQL.
Major new
Voting is now closed. This vote passes with 4 +1 votes and no 0 or -1
votes. Thank you to everyone who voted. Totals:
+1:
Michael Stack*
Steven Noels*
Enis Söztutar*
Devaraj Das*
* = IPMC
I'll send out an announcement and we'll push the release out once HBase
0.98.1 is released.
Thanks,
James
AM, Steven Noels wrote:
> On Mon, Mar 31, 2014, at 10:40 PM, James Taylor wrote:
>
>
> > Vote will be open for at least 72 hours. Please vote:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove (and reason why)
>
>
&
Hi everyone,
This is a call for a vote on Apache Phoenix 4.0.0 incubating RC3. Phoenix
is a SQL query engine for Apache HBase, a NoSQL data store. It is accessed
as a JDBC driver and enables querying and managing HBase tables using SQL. This
is the next major release of Phoenix compatible with the
Hi everyone,
This is a call for a vote on Apache Phoenix 3.0.0 incubating RC3. Phoenix
is a SQL query engine for Apache HBase, a NoSQL data store. It is accessed
as a JDBC driver and enables querying and managing HBase tables using SQL. This
is the next major release of Phoenix compatible with the
; On Wed, Mar 26, 2014 at 6:06 PM, James Taylor
> wrote:
> > The copyright for the bits we're bundling. See the LICENSE file I
> included
> > at the end of my email. For example:
> >
> > Guava, version 12.0.1, http://code.google.com/p/guava-libraries/
> &g
Hi Justin,
Yes, our source and binary releases have different NOTICE/LICENSE files.
The source ones are simple, as we have no dependencies. It's the binary one
I'm trying to get clarity on.
Thanks,
James
On Wed, Mar 26, 2014 at 5:09 PM, Justin Mclean wrote:
> Hi,
>
> I assuming you source and bi
do I know if something is a "required attributions"?
On Wed, Mar 26, 2014 at 6:02 PM, sebb wrote:
> On 27 March 2014 00:52, James Taylor wrote:
> > Where does the copyright information go in our case?
>
> What copyright information?
> Where was it originally?
>
>
Where does the copyright information go in our case?
On Wed, Mar 26, 2014 at 5:48 PM, sebb wrote:
> On 26 March 2014 23:55, James Taylor wrote:
> > Hello,
> > I'm getting a release ready for Apache Phoenix (incubating) and have a
> > question about where copyright
-q3mNMRQqC2vTA%40mail.gmail.com%3E
On Wed, Mar 26, 2014 at 5:38 PM, sebb wrote:
> On 26 March 2014 19:59, James Taylor wrote:
> > Below is our updated NOTICE (which includes the copyright for the bundled
> > bits) and LICENSE (minus the standard Apache 2.0 part).
> >
> >
Hello,
I'm getting a release ready for Apache Phoenix (incubating) and have a
question about where copyright information should go for our binary
distribution. It seems that there's quite a bit of variation, as all
projects are different. So I'll describe our binary distribution, and
perhaps others
ks,
James
On Wed, Mar 26, 2014 at 3:04 PM, James Taylor wrote:
> Thanks, Marvin. So remove the copyrights from NOTICE. Are they required
> anywhere then, as their not in the LICENSE file?
>
>
> On Wed, Mar 26, 2014 at 2:57 PM, Marvin Humphrey
> wrote:
>
>> On Wed, Ma
Thanks, Marvin. So remove the copyrights from NOTICE. Are they required
anywhere then, as their not in the LICENSE file?
On Wed, Mar 26, 2014 at 2:57 PM, Marvin Humphrey wrote:
> On Wed, Mar 26, 2014 at 12:59 PM, James Taylor
> wrote:
> > Below is our updated NOTICE (which
Below is our updated NOTICE (which includes the copyright for the bundled
bits) and LICENSE (minus the standard Apache 2.0 part).
Would appreciate a review.
Thanks,
James
* NOTICE **
Apache Phoenix (Incubating)
Copyright 2014 The Apache Software F
Thanks for all the feedback. We'll spin up another RC shortly for our 3.0
and 4.0 release with the corrections to our NOTICE and LICENSE files, along
with ensuring that our source release matches the source bundle exactly.
One question: given that we'll indicate the bundled products and their
lice
On Tue, Mar 25, 2014 at 5:35 PM, Andrew Purtell wrote:
> On Tue, Mar 25, 2014 at 4:25 PM, sebb wrote:
>
> > > Yes, we bundle ANTLR in our binary distribution. Most of the other
> items
> > > are pulled in based on the transitive dependencies of other jars we've
> > > bundled in our binary distri
On Tue, Mar 25, 2014 at 5:28 PM, sebb wrote:
> On 26 March 2014 00:23, James Taylor wrote:
> > I think I was confused by the
> > http://www.apache.org/dev/licensing-howto.html#deps-of-depsinstructions.
>
> What is confusing about that?
> If it is not clear, how could it
On Tue, Mar 25, 2014 at 5:07 PM, sebb wrote:
>
>
> HBase is ASF code surely?
> So why does it need mentioning? - unless its NOTICE file has some
> attributions that relate to what you are bundling
>
Yes, HBase is ASF code. The other stuff we've listed are the transitive
dependencies of HBase. Do
(sorry, meant instead of listing these in our NOTICE file)
On Tue, Mar 25, 2014 at 4:48 PM, James Taylor wrote:
> Ah, I see. Thanks, Sebb. So we should modify our LICENSE file as indicated
> in http://www.apache.org/dev/licensing-howto.html#permissive-deps instead
> of listing the
t that invokes it - would that be correct?
For our HBase dependencies, we have many places in the source that call
HBase APIs. Do we just list one of them?
On Tue, Mar 25, 2014 at 4:25 PM, sebb wrote:
> On 25 March 2014 23:06, James Taylor wrote:
> > Our binary distribution bundle
trying to follow the guidelines listed here[1].
Thanks,
James
[1] http://www.apache.org/dev/licensing-howto.html
On Tue, Mar 25, 2014 at 3:48 PM, sebb wrote:
> On 25 March 2014 22:27, James Taylor wrote:
> > Thanks for the detailed review, Sebb. We really appreciate you spending
> > y
0.0) at the same time?
> Or maybe my gmail thread history is messed up.
>
> - Henry
>
> On Tue, Mar 25, 2014 at 9:46 AM, James Taylor
> wrote:
> > Hi everyone,
> > This is a call for a vote on Apache Phoenix 4.0.0 incubating RC1. Phoenix
> > is a SQL query eng
hy the Git tag does not agree
> > with the source archive, otherwise the new RC may also be faulty in
> > that regard.
> >
> > It's vital that all files in the source bundle can be traced back to
> > the source code control system.
> >
> > >
Hi everyone,
This is a call for a vote on Apache Phoenix 4.0.0 incubating RC1. Phoenix
is a SQL query engine for Apache HBase, a NoSQL data store. It is accessed
as a JDBC driver and enables querying and managing HBase tables using SQL. This
is the next major release of Phoenix compatible with the
Hi everyone,
This is a call for a vote on Apache Phoenix 3.0.0 incubating RC1. Phoenix
is a SQL query engine for Apache HBase, a NoSQL data store. It is accessed
as a JDBC driver and enables querying and managing HBase tables using SQL. This
is the next major release of Phoenix compatible with the
Hello,
The Apache Phoenix team is pleased to announce the release of version
2.2.3-incubating from the Apache Incubator. Phoenix is a SQL query engine
for Apache HBase, a NoSQL data store. It is accessed as a JDBC driver and
enables querying and managing HBase tables using SQL.
The source and bin
the ticket to address the Disclaimer file for the release.
>
> On Thursday, March 13, 2014, James Taylor wrote:
>
> > Voting is now closed. This vote passes with 4 binding +1 votes and no 0
> > or -1 votes. Thank you to everyone who voted. Totals:
> >
> > +1:
&
).
> >
> > - Checked the src and binary artifacts.
> > - Checked sigs
> > - Checked CRCs
> > - Built the src artifacts
> >
> > If the DISCLAIMER file will not sink the RC, lets go ahead with releasing
> > this. Otherwise we would need a new RC.
> >
> >
Would it be possible for an IPMC member to clarify if you're waiting on us
for something and if so what?
Thanks,
James
On Tue, Mar 11, 2014 at 11:11 AM, James Taylor wrote:
> Thanks, Marvin. We'll update this in our next release too, as we'd like to
> follow the preferred
Thanks, Marvin. We'll update this in our next release too, as we'd like to
follow the preferred path.
With these changes for our next release, are we good to go for this release?
Thanks,
James
On Tue, Mar 11, 2014 at 9:40 AM, Marvin Humphrey wrote:
> On Tue, Mar 11, 2014 at 9
n Mon, Mar 10, 2014 at 10:33 PM, James Taylor
> wrote:
> > Thanks for the review, David. We do have a NOTICE.txt in both the source
> > and binary tar ball (in the phoenix-2.2.3-incubating directory). Is that
> > the correct way to do it?
> >
> > We'll add the
e.
Thanks,
James
On Mon, Mar 10, 2014 at 6:18 PM, David Nalley wrote:
> On Fri, Mar 7, 2014 at 1:43 PM, James Taylor
> wrote:
> > Hello Everyone,
> > This is a call for a vote on Apache Phoenix 2.2.3 incubating RC4. Phoenix
> > is a SQL query engine for Apache HBase, a
Hello Everyone,
This is a call for a vote on Apache Phoenix 2.2.3 incubating RC4. Phoenix
is a SQL query engine for Apache HBase, a NoSQL data store. It is accessed
as a JDBC driver and enables querying and managing HBase tables using SQL. This
will be our first release in the incubator. The releas
Cancelling this vote due to mistakes in the LICENSE and NOTICE files. Will
start a new vote shortly.
Thanks,
James
On Wed, Feb 26, 2014 at 11:08 AM, David Nalley wrote:
> On Wed, Feb 26, 2014 at 1:43 PM, James Taylor
> wrote:
> > Thanks so much, David for the review and words of e
Thanks so much, David for the review and words of encouragement. Don't
worry, we won't get discouraged - we just want to get this right.
See below for more questions/comments.
Regards,
James
On Tue, Feb 25, 2014 at 9:26 PM, David Nalley wrote:
> On Mon, Feb 24, 2014 at 9:37 PM,
Hello everyone,
This is a call for a vote on Apache Phoenix 2.2.3 incubating. Phoenix is a
SQL query engine for Apache HBase, a NoSQL data store. It is accessed as a
JDBC driver and enables querying and managing HBase tables using SQL. This
will be our first release in the incubator.
The RC is a
This vote is being cancelled because the RC did not include a source-only
tar ball. A new vote thread will be started with one that does.
Regards,
James
On Fri, Feb 21, 2014 at 5:12 PM, James Taylor wrote:
> Hello everyone,
>
> This is a call for a vote on Apache Phoenix 2.2.3 i
I'll cancel this vote and start a vote on a new RC shortly. There was a
pretty serious bug that was found in this one anyway.
Is it best practice to have a separate source-only tar bar and not include
the source in the binary tar ball? Or should it be included in both?
Thanks,
James
On Mon, Feb
Hello everyone,
This is a call for a vote on Apache Phoenix 2.2.3 incubating. Phoenix is a
SQL query engine for Apache HBase, a NoSQL data store. It is accessed as a
JDBC driver and enables querying and managing HBase tables using SQL. This
will be our first release in the incubator.
The RC is a
FYI, we have an on-going thread for the git/github discussion here:
http://mail-archives.apache.org/mod_mbox/incubator-general/201402.mbox/%3CCAEWfVJ%3D_wtDRTNEz4ojvUBf50_VdLDUhiQ15q5rfvFi5eh76uw%40mail.gmail.com%3E
For Phoenix, we'll likely mimic what JClouds is doing, but I live Lar's
ideas as a
The Phoenix project has recently come into incubation from it's former life
as a Github project. I believe other projects have made this same
transition, so I'm looking to get some advice from them. What's the best
development methodology folks have found for collaborative development when
your sou
1 - 100 of 111 matches
Mail list logo
