Filed this: https://issues.apache.org/jira/browse/PHOENIX-830
And David Nalley send us a patch already (thanks, David!) which will be
applied shortly: https://github.com/apache/incubator-phoenix/pull/20
Thanks,
James
On Thu, Mar 13, 2014 at 11:16 AM, Henry Saputra wrote:
> Please do file the t
Please do file 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:
> Michael Stack *
> Henry Saputra *
Hi James,
Sorry for the lag. I personally think that the disclaimer isn't
negotiable in an incubator release, but that's my personal opinion.
You have 4 binding +1s now, so you can ignore my opinion :) I
understand others points of view on the matter, and there's a good
reason we don't have vetoe
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:
Michael Stack *
Henry Saputra *
Enis Söztutar *
Andrew Purtell *
0:
-1:
* = binding
Thanks,
James
On Thu, Mar 13, 2014 at 8:58 AM, Henry Saputra wrote:
> Hi Enis,
Hi Enis, thx for the Vote.
There was already "commitment" from James to fix the disclaimer so I would
not think this should be a release blocker.
Thx,
Henry
On Wednesday, March 12, 2014, Enis Söztutar wrote:
> +1 (binding).
>
> - Checked the src and binary artifacts.
> - Checked sigs
> - Chec
Yes, +1. Hashes and signature looks good, tarball structure is good, and I
can successfully build and test the release from the sources.
On Wednesday, March 12, 2014, Henry Saputra wrote:
> HI Andrew,
>
> Yeah, probably need to file JIRA to track this to make sure it is
> included in next propo
+1 (binding).
- 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.
Enis
On Tue, Mar 11, 2014 at 11:11 AM, James Taylor wrote:
> Thanks,
HI Andrew,
Yeah, probably need to file JIRA to track this to make sure it is
included in next proposed release.
I am assuming this RC have your +1 Vote?
- Henry
On Mon, Mar 10, 2014 at 6:58 PM, Andrew Purtell
wrote:
> Let's also change the Phoenix POM to not exclude the files in examples/ si
Signatures looks ok
Hashes looks ok
Notice and License files looks good.
+1 (binding)
For next release it would be better to have more mentors VOTE on the
release to oversee the proposed artifacts before going to general@
list.
Should help catching missing DISCLAIMER file.
Good luck guys.
- He
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 path.
>
> With these c
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:18 AM, James Tayl
On Tue, Mar 11, 2014 at 9:18 AM, James Taylor wrote:
> Also, should we drop the ".txt"
> extension on the NOTICE and LICENSE files for our next release?
http://www.apache.org/dev/apply-license.html#license-file-name
Can the LICENSE and NOTICE files be called LICENSE.txt and NOTICE.txt?
David,
Would it be possible to get a +1 for this release provided we add the
DISCLAIMER file in our next release? Also, should we drop the ".txt"
extension on the NOTICE and LICENSE files for our next release?
Thanks,
James
On Tue, Mar 11, 2014 at 4:55 AM, David Nalley wrote:
> On Mon, Mar 10,
On 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 missing license headers in those couple of examp
Let's also change the Phoenix POM to not exclude the files in examples/ since
they have been raised as an issue more than once, if I guess correctly here.
> On 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
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 missing license headers in those couple of example files
where it's missing for our next release.
Thanks,
James
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 NoSQL data store. It is accessed
> as a JDBC driver and enables querying and managing HBase tables using SQL
+1
Ran unit tests, checked hash, and checked for license compliance.
This is a repeat of my vote from over on the phoenix list.
St.Ack
On Fri, Mar 7, 2014 at 10:43 AM, James Taylor wrote:
> Hello Everyone,
> This is a call for a vote on Apache Phoenix 2.2.3 incubating RC4. Phoenix
> is a SQL
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
19 matches
Mail list logo
