Re: [VOTE] Release Apache ServiceComb Saga (incubating) version 0.2.0

[Willem Jiang]

I mean +1 (binding).


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, Jun 13, 2018 at 9:15 AM, Willem Jiang 
wrote:

> Carrying my vote over form the dev list.
>
> I checked:
> - incubating in binary and src kit name
> - signatures and hashes correct
> - LICENSE is fine (third party jars versions are updated)
> - NOTICE is OK but has wrong year please fix
> - no unexpected binary files
> - source files have headers
> - can build the kit from source without any error
> - can run the demo with the instruction of README
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, Jun 12, 2018 at 5:12 PM, Mohammad Asif Siddiqui <
> asifdxtr...@apache.org> wrote:
>
>> Hello All,
>>
>> This is a call for vote to release Apache ServiceComb Saga (Incubating)
>> version 0.2.0
>>
>> Apache ServiceComb (Incubating) Community has voted and approved the
>> release.
>>
>> Vote Thread : https://lists.apache.org/threa
>> d.html/fd0c4593d8574563e1a247cf2bed5a72d66a317472e4d9ee59743
>> 3fc@%3Cdev.servicecomb.apache.org%3E
>>
>> Result Thread : https://lists.apache.org/threa
>> d.html/77f0360d12ca2352c9052a112ba0e4f06c028132909f84d71eca3
>> bcd@%3Cdev.servicecomb.apache.org%3E
>>
>> Release Notes : https://issues.apache.org/jira
>> /secure/ReleaseNote.jspa?projectId=12321626=12342425
>>
>> Release Candidate : https://dist.apache.org/repos/
>> dist/dev/incubator/servicecomb/incubator-servicecomb-saga/0.2.0/rc-01/
>>
>> Staging Repo : https://repository.apache.org/
>> content/repositories/orgapacheservicecomb-1271/
>>
>> Release Tag : https://github.com/apache/incu
>> bator-servicecomb-saga/releases/tag/0.2.0
>>
>> Release CommitID : 1f3c3d1e61a6c7f40df479a43d28b54f335d84ac
>>
>> Keys to verify the Release Candidate : https://dist.apache.org/repos/
>> dist/dev/incubator/servicecomb/KEYS
>>
>> Voting will start now ( Tuesday, 12th June, 2018) and will remain open
>> for next 72 hours, We request all IPMC members to give their vote.
>>
>> [ ] +1 Release this package as 0.2.0
>> [ ] +0 No Opinion
>> [ ] -1 Do not release this package because
>>
>> On the behalf of ServiceComb Team
>> Mohammad Asif Siddiqui
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>

Re: [VOTE] Release Apache ServiceComb Saga (incubating) version 0.2.0

[Willem Jiang]

Carrying my vote over form the dev list.

I checked:
- incubating in binary and src kit name
- signatures and hashes correct
- LICENSE is fine (third party jars versions are updated)
- NOTICE is OK but has wrong year please fix
- no unexpected binary files
- source files have headers
- can build the kit from source without any error
- can run the demo with the instruction of README


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Jun 12, 2018 at 5:12 PM, Mohammad Asif Siddiqui <
asifdxtr...@apache.org> wrote:

> Hello All,
>
> This is a call for vote to release Apache ServiceComb Saga (Incubating)
> version 0.2.0
>
> Apache ServiceComb (Incubating) Community has voted and approved the
> release.
>
> Vote Thread : https://lists.apache.org/thread.html/
> fd0c4593d8574563e1a247cf2bed5a72d66a317472e4d9ee597433fc@%
> 3Cdev.servicecomb.apache.org%3E
>
> Result Thread : https://lists.apache.org/thread.html/
> 77f0360d12ca2352c9052a112ba0e4f06c028132909f84d71eca3bcd@%
> 3Cdev.servicecomb.apache.org%3E
>
> Release Notes : https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12321626=12342425
>
> Release Candidate : https://dist.apache.org/repos/dist/dev/incubator/
> servicecomb/incubator-servicecomb-saga/0.2.0/rc-01/
>
> Staging Repo : https://repository.apache.org/content/repositories/
> orgapacheservicecomb-1271/
>
> Release Tag : https://github.com/apache/incubator-servicecomb-saga/
> releases/tag/0.2.0
>
> Release CommitID : 1f3c3d1e61a6c7f40df479a43d28b54f335d84ac
>
> Keys to verify the Release Candidate : https://dist.apache.org/repos/
> dist/dev/incubator/servicecomb/KEYS
>
> Voting will start now ( Tuesday, 12th June, 2018) and will remain open for
> next 72 hours, We request all IPMC members to give their vote.
>
> [ ] +1 Release this package as 0.2.0
> [ ] +0 No Opinion
> [ ] -1 Do not release this package because
>
> On the behalf of ServiceComb Team
> Mohammad Asif Siddiqui
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m2

[Willem Jiang]

+1 (binding)

Carrying my vote over form the dev list.

For the source code I checked:
1. File name with incubating
2. Signed key and sha file are OK
3. License and Notice file is good
4. RAT check OK
5. DISCLAME file is there
6. No other code in the vendor directory

For the binary I checked:
1. File name with incubating
2. Signed key and sha file are OK
3. License for the go files includes the hash commit info
4. License for the frondend js includes the js version
5. Notice file is fine
6. DISCLAME file is right
7. The Server and Frondend can be started with instruction of README.



Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Jun 12, 2018 at 4:36 PM, Mohammad Asif Siddiqui <
asifdxtr...@apache.org> wrote:

> Hello All,
>
> This is a call for vote to release Apache ServiceComb Service-Center
> (Incubating) version 1.0.0-m2.
>  Apache ServiceComb (Incubating) Community has voted and approved the
> release
>
> Vote Thread : https://lists.apache.org/thread.html/
> 2c979af45fd37ecf944c783844240f3874b96713997f2fc2a0bd71fc@%
> 3Cdev.servicecomb.apache.org%3E
>
> Result Thread : https://lists.apache.org/thread.html/
> 2b7548c13deec4f563c41d3cc6daab16fd3b691ec9b48bd54caad2d8@%
> 3Cdev.servicecomb.apache.org%3E
>
> Release Notes : https://github.com/apache/incubator-servicecomb-service-
> center/blob/master/docs/release/releaseNotes-1.0.0-m2.md
>
> Release Candidate : https://dist.apache.org/repos/dist/dev/incubator/
> servicecomb/incubator-servicecomb-service-center/1.0.0-m2/rc-01/
>
> Release Tag : https://github.com/apache/incubator-servicecomb-service-
> center/releases/tag/1.0.0-m2
>
> Release CommitID : b913a2de1b5f7fb2a42ac719fe5891d5f46f349d
>
> Keys to verify the Release Candidate : https://dist.apache.org/repos/
> dist/dev/incubator/servicecomb/KEYS
>
> Guide to build the release from source : https://github.com/apache/
> incubator-servicecomb-service-center/tree/master/scripts/release
>
> Voting will start now(Tuesday, 12th June, 2018) and will remain open for
> next 72 hours, Request all IPMC members to give their vote.
>
> [ ] +1 Release this package as 1.0.0-m2
> [ ] +0 No Opinion
> [ ] -1 Do not release this package because...
>
> On the behalf of ServiceComb Team
> Mohammad Asif Siddiqui
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Looking for Champion

[Li,De(BDG)]

Hi Julian,

Thank you.

It looks like that we have to find another one.
If anyone has a good name, please feel free to let me know.

Best Regards,
Reed

在 2018/6/13 上午4:20， "Julian Hyde"  写入:

>Note that there is an existing database product called Palo - an open
>source OLAP engine by German company Jedox[1]. There there is a high
>likelihood that Palo would have to change its name during incubation, if
>accepted.
>
>Julian
>
>[1] https://en.wikipedia.org/wiki/Palo_(OLAP_database)
>
>
>
>
>> On Jun 10, 2018, at 3:49 AM, Han Luke  wrote:
>> 
>> Cool Dave, it’s great to have you to be the campaign.
>> 
>> 
>> 
>> From: Tan,Zhongyi mailto:tanzhon...@baidu.com>>
>> Sent: Saturday, June 9, 2018 8:16:28 AM
>> To: general@incubator.apache.org 
>> Subject: Re: Looking for Champion
>> 
>> thanks，willem
>> 
>> we are very appreciate.
>> 
>>> 在 2018年6月8日，23:03，Willem Jiang  写道：
>>> 
>>> Hi,
>>> 
>>> I'm willing to be the Mentor.
>>> Please count me in.
>>> 
>>> 
>>> 
>>> Willem Jiang
>>> 
>>> Twitter: willemjiang
>>> Weibo: 姜宁willem
>>> 
 On Fri, Jun 8, 2018 at 8:59 PM, Dave Fisher 
wrote:
 
 Hi -
 
 I’m willing to Champion and Mentor. I have a couple of comments
inline.
 I’ll look at dependency licenses later today. It’s early for me.
 
 
> On Jun 7, 2018, at 9:45 PM, Li,De(BDG)  wrote:
> 
> Hi all,
> 
> I am Reed, as a developer worked with the team for Palo (a MPP-based
 interactive SQL data warehousing).
> https://github.com/baidu/palo/wiki/Palo-Overview
> 
> We propose to contribute Palo as an Apache Incubator project, and
> we are still looking for possible Champion if anyone would like to
 volunteer. Thanks a lot.
> 
> Best Regards,
> Reed
> 
> ===
> The draft of the proposal as below:
> 
> #Apache Palo
> 
> ##Abstract
> 
> Palo is a MPP-based interactive SQL data warehousing for reporting
>and
 analysis.
> 
> ##Proposal
> 
> We propose to contribute the Palo codebase and associated artifacts
 (e.g. documentation, web-site content etc.) to the Apache Software
 Foundation with the intent of forming a productive, meritocratic and
open
 community around Palo’s continued development, according to the
‘Apache
 Way’.
> 
> Baidu owns several trademarks regarding Palo, and proposes to
>transfer
 ownership of those trademarks in full to the ASF.
> 
> ###Overview of Palo
> 
> Palo’s implementation consists of two daemons: Frontend (FE) and
>Backend
 (BE).
> 
> **Frontend daemon** consists of query coordinator and catalog
>manager.
 Query coordinator is responsible for receiving users’ sql queries,
 compiling queries and managing queries execution. Catalog manager is
 responsible for managing metadata such as databases, tables,
partitions,
 replicas and etc. Several frontend daemons could be deployed to
guarantee
 fault-tolerance, and load balancing.
> 
> **Backend daemon** stores the data and executes the query fragments.
 Many backend daemons could also be deployed to provide scalability and
 fault-tolerance.
> 
> A typical Palo cluster generally composes of several frontend daemons
 and dozens to hundreds of backend daemons.
> 
> Users can use MySQL client tools to connect any frontend daemon to
 submit SQL query. Frontend receives the query and compiles it into
query
 plans executable by the Backend. Then Frontend sends the query plan
 fragments to Backend. Backend will build a query execution DAG. Data
is
 fetched and pipelined into the DAG. The final result response is sent
to
 client via Frontend. The distribution of query fragment execution
takes
 minimizing data movement and maximizing scan locality as the main
goal.
> 
> ##Background
> 
> At Baidu, Prior to Palo, different tools were deployed to solve
>diverse
 requirements in many ways. And when a use case requires the
simultaneous
 availability of capabilities that cannot all be provided by a single
tool,
 users were forced to build hybrid architectures that stitch multiple
tools
 together, but we believe that they shouldn’t need to accept such
inherent
 complexity. A storage system built to provide great performance
across a
 broad range of workloads provides a more elegant solution to the
problems
 that hybrid architectures aim to solve. Palo is the solution.
> 
> Palo is designed to be a simple and single tightly coupled system,
>not
 depending on other systems. Palo provides high concurrent low latency
point
 query performance, but also provides high throughput queries of ad-hoc
 

Re: Looking for Champion

[Julian Hyde]

Note that there is an existing database product called Palo - an open source 
OLAP engine by German company Jedox[1]. There there is a high likelihood that 
Palo would have to change its name during incubation, if accepted.

Julian

[1] https://en.wikipedia.org/wiki/Palo_(OLAP_database) 




> On Jun 10, 2018, at 3:49 AM, Han Luke  wrote:
> 
> Cool Dave, it’s great to have you to be the campaign.
> 
> 
> 
> From: Tan,Zhongyi mailto:tanzhon...@baidu.com>>
> Sent: Saturday, June 9, 2018 8:16:28 AM
> To: general@incubator.apache.org 
> Subject: Re: Looking for Champion
> 
> thanks，willem
> 
> we are very appreciate.
> 
>> 在 2018年6月8日，23:03，Willem Jiang  写道：
>> 
>> Hi,
>> 
>> I'm willing to be the Mentor.
>> Please count me in.
>> 
>> 
>> 
>> Willem Jiang
>> 
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>> 
>>> On Fri, Jun 8, 2018 at 8:59 PM, Dave Fisher  wrote:
>>> 
>>> Hi -
>>> 
>>> I’m willing to Champion and Mentor. I have a couple of comments inline.
>>> I’ll look at dependency licenses later today. It’s early for me.
>>> 
>>> 
 On Jun 7, 2018, at 9:45 PM, Li,De(BDG)  wrote:
 
 Hi all,
 
 I am Reed, as a developer worked with the team for Palo (a MPP-based
>>> interactive SQL data warehousing).
 https://github.com/baidu/palo/wiki/Palo-Overview
 
 We propose to contribute Palo as an Apache Incubator project, and
 we are still looking for possible Champion if anyone would like to
>>> volunteer. Thanks a lot.
 
 Best Regards,
 Reed
 
 ===
 The draft of the proposal as below:
 
 #Apache Palo
 
 ##Abstract
 
 Palo is a MPP-based interactive SQL data warehousing for reporting and
>>> analysis.
 
 ##Proposal
 
 We propose to contribute the Palo codebase and associated artifacts
>>> (e.g. documentation, web-site content etc.) to the Apache Software
>>> Foundation with the intent of forming a productive, meritocratic and open
>>> community around Palo’s continued development, according to the ‘Apache
>>> Way’.
 
 Baidu owns several trademarks regarding Palo, and proposes to transfer
>>> ownership of those trademarks in full to the ASF.
 
 ###Overview of Palo
 
 Palo’s implementation consists of two daemons: Frontend (FE) and Backend
>>> (BE).
 
 **Frontend daemon** consists of query coordinator and catalog manager.
>>> Query coordinator is responsible for receiving users’ sql queries,
>>> compiling queries and managing queries execution. Catalog manager is
>>> responsible for managing metadata such as databases, tables, partitions,
>>> replicas and etc. Several frontend daemons could be deployed to guarantee
>>> fault-tolerance, and load balancing.
 
 **Backend daemon** stores the data and executes the query fragments.
>>> Many backend daemons could also be deployed to provide scalability and
>>> fault-tolerance.
 
 A typical Palo cluster generally composes of several frontend daemons
>>> and dozens to hundreds of backend daemons.
 
 Users can use MySQL client tools to connect any frontend daemon to
>>> submit SQL query. Frontend receives the query and compiles it into query
>>> plans executable by the Backend. Then Frontend sends the query plan
>>> fragments to Backend. Backend will build a query execution DAG. Data is
>>> fetched and pipelined into the DAG. The final result response is sent to
>>> client via Frontend. The distribution of query fragment execution takes
>>> minimizing data movement and maximizing scan locality as the main goal.
 
 ##Background
 
 At Baidu, Prior to Palo, different tools were deployed to solve diverse
>>> requirements in many ways. And when a use case requires the simultaneous
>>> availability of capabilities that cannot all be provided by a single tool,
>>> users were forced to build hybrid architectures that stitch multiple tools
>>> together, but we believe that they shouldn’t need to accept such inherent
>>> complexity. A storage system built to provide great performance across a
>>> broad range of workloads provides a more elegant solution to the problems
>>> that hybrid architectures aim to solve. Palo is the solution.
 
 Palo is designed to be a simple and single tightly coupled system, not
>>> depending on other systems. Palo provides high concurrent low latency point
>>> query performance, but also provides high throughput queries of ad-hoc
>>> analysis. Palo provides bulk-batch data loading, but also provides near
>>> real-time mini-batch data loading. Palo also provides high availability,
>>> reliability, fault tolerance, and scalability.
 
 ##Rationale
 
 Palo mainly integrates the technology of Google Mesa and Apache Impala.
 
 Mesa is a highly scalable analytic data storage system that stores
>>> critical measurement data related to 

Re: [VOTE] Pulsar Release 1.22.1-incubating Candidate 2

[Jai Asher]

The vote for releasing Apache Pulsar 1.22.1-incubating is now closed.

With a total of +3 binding votes and no -1 votes, the vote passes.

+1s (binding):
Dave
Justin
Jim

This is the link to the dev@ vote thread for the same, will update the
release process to add this link in the initial mail next release onwards -
Thanks Dave for pointing this out.
https://lists.apache.org/thread.html/27dbe3f467d2df18bf2799b480d66194bf8943f7fd764ecb9d15773c@%3Cdev.pulsar.apache.org%3E

Thanks, Yang, Justin and Craig for your inputs on the ASF and BSD header -
we will correct these files by removing ASF header, leaving only BSD header.


On Mon, Jun 11, 2018 at 9:30 AM, Matteo Merli  wrote:

> Thanks Yang, Justin and Craig for the discussion.
>
> We will correct these files by removing ASF header, leaving only BSD header
> + comment.
>
> Matteo
>
> On Sun, Jun 10, 2018 at 9:59 AM Craig Russell 
> wrote:
>
> > I'll add my own chimes to this discussion.
> >
> > > On Jun 10, 2018, at 2:57 AM, Justin Mclean 
> > wrote:
> > > ...
> > > I think I agree with Matteo that those protobuf files should not have
> an
> > ASF header. Generally changes to a file are under the original license,
> see
> > [1], but it not a big issue as BSD is an Category A license and you are
> > including the full license text. It’s also seems odd because the license
> > calls them out as BSD licensed.
> >
> > Yes, these files are not being relicensed. Files that are covered by an
> > ICLA by the original author, or covered by a software grant can be
> > relicensed. In that case, removing the BSD license header and replacing
> it
> > by the Apache license header is appropriate.
> >
> > In this case of a BSD-licensed file that has minor changes, the Apache
> > license header is inappropriate. The only part of the file that is
> > Apache-licensed is the changes made here. So the Apache license header
> that
> > states that this file is "Licensed to the Apache Software Foundation ...
> > under one or more contributor license agreements" is not correct.
> >
> > The comment line "This file is derived from Google ProcolBuffer
> > CodedInputStream class" is sufficient documentation, without the Apache
> > license header.
> >
> > Regards,
> >
> > Craig
> >
> > >
> > > Thanks,
> > > Justin
> > >
> > > 1. https://www.apache.org/legal/src-headers.html#3party
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> > Craig L Russell
> > Secretary, Apache Software Foundation
> > c...@apache.org http://db.apache.org/jdo
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> > --
> Matteo Merli
> 
>

[VOTE] Release Apache ServiceComb Saga (incubating) version 0.2.0

[Mohammad Asif Siddiqui]

Hello All,  
  
This is a call for vote to release Apache ServiceComb Saga (Incubating) version 
0.2.0  
  
Apache ServiceComb (Incubating) Community has voted and approved the release.  
  
Vote Thread : 
https://lists.apache.org/thread.html/fd0c4593d8574563e1a247cf2bed5a72d66a317472e4d9ee597433fc@%3Cdev.servicecomb.apache.org%3E
  
  
Result Thread : 
https://lists.apache.org/thread.html/77f0360d12ca2352c9052a112ba0e4f06c028132909f84d71eca3bcd@%3Cdev.servicecomb.apache.org%3E
  
  
Release Notes : 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12342425
  
  
Release Candidate : 
https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-saga/0.2.0/rc-01/
  
  
Staging Repo : 
https://repository.apache.org/content/repositories/orgapacheservicecomb-1271/ 
   
Release Tag : 
https://github.com/apache/incubator-servicecomb-saga/releases/tag/0.2.0  
  
Release CommitID : 1f3c3d1e61a6c7f40df479a43d28b54f335d84ac  
  
Keys to verify the Release Candidate : 
https://dist.apache.org/repos/dist/dev/incubator/servicecomb/KEYS  
  
Voting will start now ( Tuesday, 12th June, 2018) and will remain open for next 
72 hours, We request all IPMC members to give their vote.  
  
[ ] +1 Release this package as 0.2.0  
[ ] +0 No Opinion  
[ ] -1 Do not release this package because  
  
On the behalf of ServiceComb Team  
Mohammad Asif Siddiqui  
 

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

[VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m2

[Mohammad Asif Siddiqui]

Hello All,  
  
This is a call for vote to release Apache ServiceComb Service-Center 
(Incubating) version 1.0.0-m2. 
 Apache ServiceComb (Incubating) Community has voted and approved the release  
  
Vote Thread : 
https://lists.apache.org/thread.html/2c979af45fd37ecf944c783844240f3874b96713997f2fc2a0bd71fc@%3Cdev.servicecomb.apache.org%3E
  
  
Result Thread : 
https://lists.apache.org/thread.html/2b7548c13deec4f563c41d3cc6daab16fd3b691ec9b48bd54caad2d8@%3Cdev.servicecomb.apache.org%3E
  
  
Release Notes : 
https://github.com/apache/incubator-servicecomb-service-center/blob/master/docs/release/releaseNotes-1.0.0-m2.md
  
  
Release Candidate : 
https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-service-center/1.0.0-m2/rc-01/
  
  
Release Tag : 
https://github.com/apache/incubator-servicecomb-service-center/releases/tag/1.0.0-m2
 
   
Release CommitID : b913a2de1b5f7fb2a42ac719fe5891d5f46f349d  
  
Keys to verify the Release Candidate : 
https://dist.apache.org/repos/dist/dev/incubator/servicecomb/KEYS  
  
Guide to build the release from source : 
https://github.com/apache/incubator-servicecomb-service-center/tree/master/scripts/release
  
  
Voting will start now(Tuesday, 12th June, 2018) and will remain open for next 
72 hours, Request all IPMC members to give their vote.  
  
[ ] +1 Release this package as 1.0.0-m2  
[ ] +0 No Opinion  
[ ] -1 Do not release this package because...  
  
On the behalf of ServiceComb Team  
Mohammad Asif Siddiqui  


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