You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brpc.apache.org by tan zhongyi <zh...@gmail.com> on 2019/03/18 15:26:26 UTC
the tasklist that needed for the first apache release
Hi， guys,
We need to release our first apache release for brpc in Q2.
And it will be a great step to be an TOP level apache project for brpc.
Here is some tasks that need to be done for the release after I refer to document from apache.org
1. Get all dependency third party’s copyright and apppend them to brpc License file
2. Add Notice and Disclaimer file to mention its copyright belong to apache foundation
3. Make a short license header, and add the header to all source files, including .h, .cpp, .java, etc
4. Check the source tarball to make sure it does not contain binary files except for data
5. Prepare release note to list all import checkin and features
6. Update Readme to add one section as “How to build”
When we finish these tasks, then we need to open a thread to vote on dev@brpc.apache.org<ma...@brpc.apache.org>,
If got approved, we need to open another vote on incubator mail list.
If not approved, we should make changes according to our mentor or other’s suggestion, and vote again.
I remember that it is very common to have several vote for the first release.
That’s all for a release, anyone have comments?
Thanks
Re: help about apache permitted license
Posted by "Tan,Zhongyi" <ta...@baidu.com>.
Hi， James，
How about this suggestion?
Using apr's time instead of nspr's time
Thanks'
在 2019/3/28 上午2:23，“Dave Fisher”<da...@comcast.net> 写入:
Hi -
Have a look at the Apache Portable Runtime’s time routines.
https://apr.apache.org/docs/apr/1.5/group__apr__time.html
Regards,
Dave
Sent from my iPhone
> On Mar 27, 2019, at 1:55 AM, tan zhongyi <zh...@gmail.com> wrote:
>
> Hi£¬ guys,
>
> Here is one issue that may block our first apache release
>
> I checked the code, notice we are using nspr,
> /src/butil/third_party/nspr/prtime.h
> /src/butil/third_party/nspr/prtime.cc
> /src/butil/third_party/nspr/LICENSE
>
> From their HEAD, we know that
> They are Dual-license, GPL-2.0+, LGPL-2.1+, MPL-1.1
>
> GPL & LGPL are not allowed for apache release,
> But how about MPL-1.1?
>
> Can we include these three files?
>
> Thanks
>
>
>
> ?B‹KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB•?È?[œÝXœØÜšX™K??K[XZ[?ˆ??]‹][œÝXœØÜšX™P?œœ?˘\?XÚ?K›Ü™ÃB‘›Üˆ?Y??]?[Û˜[??ÛÛ[X[™?Ë??K[XZ[?ˆ??]‹Z?[???œœ?˘\?XÚ?K›Ü™ÃB
Re: help about apache permitted license
Posted by Dave Fisher <da...@comcast.net>.
Hi -
Have a look at the Apache Portable Runtime’s time routines.
https://apr.apache.org/docs/apr/1.5/group__apr__time.html
Regards,
Dave
Sent from my iPhone
> On Mar 27, 2019, at 1:55 AM, tan zhongyi <zh...@gmail.com> wrote:
>
> Hi£¬ guys,
>
> Here is one issue that may block our first apache release
>
> I checked the code, notice we are using nspr,
> /src/butil/third_party/nspr/prtime.h
> /src/butil/third_party/nspr/prtime.cc
> /src/butil/third_party/nspr/LICENSE
>
> From their HEAD, we know that
> They are Dual-license, GPL-2.0+, LGPL-2.1+, MPL-1.1
>
> GPL & LGPL are not allowed for apache release,
> But how about MPL-1.1?
>
> Can we include these three files?
>
> Thanks
>
>
>
> B‹KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB•È [œÝXœØÜšX™KK[XZ[ˆ]‹][œÝXœØÜšX™PœœË˜\XÚK›Ü™ÃB‘›ÜˆY][Û˜[ÛÛ[X[™ ËK[XZ[ˆ]‹Z[ œœË˜\XÚK›Ü™ÃB
help about apache permitted license
Posted by tan zhongyi <zh...@gmail.com>.
Hi， guys,
Here is one issue that may block our first apache release
I checked the code, notice we are using nspr,
/src/butil/third_party/nspr/prtime.h
/src/butil/third_party/nspr/prtime.cc
/src/butil/third_party/nspr/LICENSE
From their HEAD, we know that
They are Dual-license, GPL-2.0+, LGPL-2.1+, MPL-1.1
GPL & LGPL are not allowed for apache release,
But how about MPL-1.1?
Can we include these three files?
Thanks
Re: the tasklist that needed for the first apache release
Posted by "Kevin A. McGrail" <km...@apache.org>.
On 4/10/2019 8:19 AM, JiashunZhu wrote:
> I have checked other three apache projects and the comment style they use
> is /* */ .
> Should we use the same style to get consistency?
I would say that I always use like and kind styling for an existing
project. I would not worry about what other projects are doing on
that. If you like 2 tabs, 7 spaces, /* vs // etc., that's really up to
the project.
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@brpc.apache.org
For additional commands, e-mail: dev-help@brpc.apache.org
Re: the tasklist that needed for the first apache release
Posted by JiashunZhu <zh...@gmail.com>.
I have checked other three apache projects and the comment style they use
is /* */ .
Should we use the same style to get consistency?
other project file:
https://github.com/apache/spark/blob/974f52499271848705c9eb209373f27d808fb72b/sql/core/src/main/scala/org/apache/spark/sql/UDFRegistration.scala
https://github.com/apache/hbase/blob/master/hbase-thrift/src/main/java/org/apache/hadoop/hbase/thrift/Constants.java
https://github.com/apache/incubator-dubbo/blob/5298afdf401185876edd49b0ad5755f8f618e4cb/dubbo-common/src/test/java/org/apache/dubbo/common/beanutil/JavaBeanAccessorTest.java
Wang,Weibing <wa...@baidu.com> 于2019年4月10日周三 下午3:56写道：
> Hi, all
> I'd like you to review this license header. If it has no problem, I will
> add the header to all source files and replace the exist one.
>
> // Licensed to the Apache Software Foundation (ASF) under one
> // or more contributor license agreements. See the NOTICE file
> // distributed with this work for additional information
> // regarding copyright ownership. The ASF licenses this file
> // to you under the Apache License, Version 2.0 (the
> // "License"); you may not use this file except in compliance
> // with the License. You may obtain a copy of the License at
> //
> // http://www.apache.org/licenses/LICENSE-2.0
> //
> // Unless required by applicable law or agreed to in writing,
> // software distributed under the License is distributed on an
> // "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> // KIND, either express or implied. See the License for the
> // specific language governing permissions and limitations
> // under the License.
>
>
>
> 在 2019/4/9 08:46，“tan zhongyi”<zh...@gmail.com> 写入:
>
> OK, let me push us to work on our tasks.
>
>
> 在 2019/3/29 下午4:07，“tan zhongyi”<je...@apache.org> 写入:
>
> Great，thanks huwenwei.
>
> Now Let me to clarify the task of our first release
>
> 1. Get all dependency third party’s copyright and apppend them to
> brpc License file
> @ Zhangyi Chen
> Hi, zhangyi，this task is the most difficult work for this release
> You need to add every needed third party copyright into our's LICENSE
> file.
> If you have any problem, please let us know, we will help on that
>
> 2. Add Notice and Disclaimer file to mention its copyright belong
> to apache foundation
> @tanzhongyi already checked in, marked as done
>
> 3. Make a short license header, and add the header to all source
> files, including .h, .cpp, .java, etc
> @wang weibing
> Hi, weibing, would you please make a short license header for us to
> review first?
> thanks
>
> 4. Check the source tarball to make sure it does not contain
> binary files except for data
> @TanZhongyi pending
>
> 5. Prepare release note to list all import checkin and features
> @James Ge ?
> Hi, james, any progress?
>
>
> 6. Update Readme to add one section as “How to build”
> @ huwenwei
> Hi, huwenwei, any progress?
>
>
> We can start to work now, and discuss related issues in this mail
> list to keep a good record.
> Thanks
>
> The most difficult part is #1, we need to list all third party
> code into brpc's License file,
> If not permitted, we need to find another solution.
>
>
>
> 在 2019/3/29 下午2:41，“Hu,Wenwei”<hu...@baidu.com> 写入:
>
> I would like take 6.
>
>
>
> 在 2019/3/28 09:23，“tan zhongyi”<zh...@gmail.com> 写入:
>
> Thanks，zhangyi，
>
> Anyone else who want to volunteer to take some task？
>
> 在 2019/3/27 下午10:17，“Zhangyi Chen”<fr...@gmail.com>
> 写入:
>
> I would like take 1 and 2.
>
> On Tue, Mar 26, 2019 at 2:25 PM tan zhongyi <
> zhongyi.tan@gmail.com> wrote:
>
> > Hi， all，
> >
> > We need to assign task for our first release .
> > Anyone who volunteer to take ?
> > Here is the task list, you can reply with it with
> your interested task,
> > Thanks
> >
> >
> > Here is the task list：
> > 1. Get all dependency third
> party’s copyright and
> > apppend them to brpc License file
> >
> > 2. Add Notice and Disclaimer file to
> mention its copyright
> > belong to apache foundation
> >
> > 3. Make a short license header, and add
> the header to all
> > source files, including .h, .cpp, .java, etc
> >
> > 4. Check the source tarball to make sure
> it does not contain
> > binary files except for data
> >
> > 5. Prepare release note to list all
> import checkin and features
> >
> > 6. Update Readme to add one section as
> “How to build”
> >
> >
> > BTW：Here is one important things about include third
> party code:
> > From its website
> https://apache.org/legal/resolved.html
> > CATEGORY X: WHAT CAN WE NOT INCLUDE IN AN ASF
> PROJECT?¶
> > Apache project forbid some third party software
> in it, it includes:
> > 1. AGPL， LGPL，GPL
> > 2. BSD + Fackbook patient
> > 3.BSD-4-clouse
> >
> >
> >
> >
> > 在 2019/3/19 下午3:04，“tan zhongyi”<je...@apache.org>
> 写入:
> >
> > Here is one example from Doris's RD
> > Doris just released its first apache version,
> > The owner write a document step by step, very
> details
> >
> > Here it is :
> >
> http://doris.apache.org/policy/release_process.html
> >
> >
> >
> >
> >
> > 在 2019/3/18 下午11:26，“tan zhongyi”<
> zhongyi.tan@gmail.com> 写入:
> >
> > Hi， guys,
> >
> > We need to release our first apache release
> for brpc in Q2.
> >
> > And it will be a great step to be an TOP
> level apache project for
> > brpc.
> >
> > Here is some tasks that need to be done for
> the release after I
> > refer to document from apache.org
> >
> >
> > 1. Get all dependency third party’s
> copyright and apppend them
> > to brpc License file
> >
> > 2. Add Notice and Disclaimer file to
> mention its copyright
> > belong to apache foundation
> >
> > 3. Make a short license header, and add
> the header to all
> > source files, including .h, .cpp, .java, etc
> >
> > 4. Check the source tarball to make sure
> it does not contain
> > binary files except for data
> >
> > 5. Prepare release note to list all
> import checkin and features
> >
> > 6. Update Readme to add one section as
> “How to build”
> >
> >
> >
> >
> > When we finish these tasks, then we need to
> open a thread to vote
> > on dev@brpc.apache.org<ma...@brpc.apache.org>,
> > If got approved, we need to open another
> vote on incubator mail
> > list.
> > If not approved, we should make changes
> according to our mentor
> > or other’s suggestion, and vote again.
> >
> > I remember that it is very common to have
> several vote for the
> > first release.
> >
> > That’s all for a release, anyone have
> comments?
> > Thanks
> >
> >
> >
> >
>
>
> ?B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�?�?[��X��ܚX�K??K[XZ[?�??]�][��X��ܚX�P?��?˘\?X�?K�ܙ�B��܈?Y??]?[ۘ[??��[X[�?�??K[XZ[?�??]�Z?[???��?˘\?X�?K�ܙ�B
>
>
> ?B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�?�?[��X��ܚX�K??K[XZ[
> �??]�][��X��ܚX�P?��?˘\?X�?K�ܙ�B��܈?Y??]?[ۘ[??��[X[�?�??K[XZ[
> �??]�Z?[???��?˘\?X�?K�ܙ�B
>
>
> ?B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�?�?[��X��ܚX�K??K[XZ[?�??]�][��X��ܚX�P?��?˘\?X�?K�ܙ�B��܈?Y??]?[ۘ[??��[X[�?�??K[XZ[?�??]�Z?[???��?˘\?X�?K�ܙ�B
>
>
--
Jiashun Zhu
Re: the tasklist that needed for the first apache release
Posted by "Wang,Weibing" <wa...@baidu.com>.
Hi, all
I'd like you to review this license header. If it has no problem, I will add the header to all source files and replace the exist one.
// Licensed to the Apache Software Foundation (ASF) under one
// or more contributor license agreements. See the NOTICE file
// distributed with this work for additional information
// regarding copyright ownership. The ASF licenses this file
// to you under the Apache License, Version 2.0 (the
// "License"); you may not use this file except in compliance
// with the License. You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing,
// software distributed under the License is distributed on an
// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
// KIND, either express or implied. See the License for the
// specific language governing permissions and limitations
// under the License.
在 2019/4/9 08:46，“tan zhongyi”<zh...@gmail.com> 写入:
OK, let me push us to work on our tasks.
在 2019/3/29 下午4:07，“tan zhongyi”<je...@apache.org> 写入:
Great，thanks huwenwei.
Now Let me to clarify the task of our first release
1. Get all dependency third party’s copyright and apppend them to brpc License file
@ Zhangyi Chen
Hi, zhangyi，this task is the most difficult work for this release
You need to add every needed third party copyright into our's LICENSE file.
If you have any problem, please let us know, we will help on that
2. Add Notice and Disclaimer file to mention its copyright belong to apache foundation
@tanzhongyi already checked in, marked as done
3. Make a short license header, and add the header to all source files, including .h, .cpp, .java, etc
@wang weibing
Hi, weibing, would you please make a short license header for us to review first?
thanks
4. Check the source tarball to make sure it does not contain binary files except for data
@TanZhongyi pending
5. Prepare release note to list all import checkin and features
@James Ge ?
Hi, james, any progress?
6. Update Readme to add one section as “How to build”
@ huwenwei
Hi, huwenwei, any progress?
We can start to work now, and discuss related issues in this mail list to keep a good record.
Thanks
The most difficult part is #1, we need to list all third party code into brpc's License file,
If not permitted, we need to find another solution.
在 2019/3/29 下午2:41，“Hu,Wenwei”<hu...@baidu.com> 写入:
I would like take 6.
在 2019/3/28 09:23，“tan zhongyi”<zh...@gmail.com> 写入:
Thanks，zhangyi，
Anyone else who want to volunteer to take some task？
在 2019/3/27 下午10:17，“Zhangyi Chen”<fr...@gmail.com> 写入:
I would like take 1 and 2.
On Tue, Mar 26, 2019 at 2:25 PM tan zhongyi <zh...@gmail.com> wrote:
> Hi， all，
>
> We need to assign task for our first release .
> Anyone who volunteer to take ?
> Here is the task list, you can reply with it with your interested task,
> Thanks
>
>
> Here is the task list：
> 1. Get all dependency third party’s copyright and
> apppend them to brpc License file
>
> 2. Add Notice and Disclaimer file to mention its copyright
> belong to apache foundation
>
> 3. Make a short license header, and add the header to all
> source files, including .h, .cpp, .java, etc
>
> 4. Check the source tarball to make sure it does not contain
> binary files except for data
>
> 5. Prepare release note to list all import checkin and features
>
> 6. Update Readme to add one section as “How to build”
>
>
> BTW：Here is one important things about include third party code:
> From its website https://apache.org/legal/resolved.html
> CATEGORY X: WHAT CAN WE NOT INCLUDE IN AN ASF PROJECT?¶
> Apache project forbid some third party software in it, it includes:
> 1. AGPL， LGPL，GPL
> 2. BSD + Fackbook patient
> 3.BSD-4-clouse
>
>
>
>
> 在 2019/3/19 下午3:04，“tan zhongyi”<je...@apache.org> 写入:
>
> Here is one example from Doris's RD
> Doris just released its first apache version,
> The owner write a document step by step, very details
>
> Here it is :
> http://doris.apache.org/policy/release_process.html
>
>
>
>
>
> 在 2019/3/18 下午11:26，“tan zhongyi”<zh...@gmail.com> 写入:
>
> Hi， guys,
>
> We need to release our first apache release for brpc in Q2.
>
> And it will be a great step to be an TOP level apache project for
> brpc.
>
> Here is some tasks that need to be done for the release after I
> refer to document from apache.org
>
>
> 1. Get all dependency third party’s copyright and apppend them
> to brpc License file
>
> 2. Add Notice and Disclaimer file to mention its copyright
> belong to apache foundation
>
> 3. Make a short license header, and add the header to all
> source files, including .h, .cpp, .java, etc
>
> 4. Check the source tarball to make sure it does not contain
> binary files except for data
>
> 5. Prepare release note to list all import checkin and features
>
> 6. Update Readme to add one section as “How to build”
>
>
>
>
> When we finish these tasks, then we need to open a thread to vote
> on dev@brpc.apache.org<ma...@brpc.apache.org>,
> If got approved, we need to open another vote on incubator mail
> list.
> If not approved, we should make changes according to our mentor
> or other’s suggestion, and vote again.
>
> I remember that it is very common to have several vote for the
> first release.
>
> That’s all for a release, anyone have comments?
> Thanks
>
>
>
>
?B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�?�?[��X��ܚX�K??K[XZ[?�??]�][��X��ܚX�P?��?˘\?X�?K�ܙ�B��܈?Y??]?[ۘ[??��[X[�?�??K[XZ[?�??]�Z?[???��?˘\?X�?K�ܙ�B
?B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�?�?[��X��ܚX�K??K[XZ[
�??]�][��X��ܚX�P?��?˘\?X�?K�ܙ�B��܈?Y??]?[ۘ[??��[X[�?�??K[XZ[
�??]�Z?[???��?˘\?X�?K�ܙ�B
?B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�?�?[��X��ܚX�K??K[XZ[?�??]�][��X��ܚX�P?��?˘\?X�?K�ܙ�B��܈?Y??]?[ۘ[??��[X[�?�??K[XZ[?�??]�Z?[???��?˘\?X�?K�ܙ�B
Hi, folks, please review pod reports
Posted by tan zhongyi <zh...@gmail.com>.
https://cwiki.apache.org/confluence/display/INCUBATOR/July2019
thanks
Re: Update for tasklist that needed for the first apache release and
target timeline
Posted by tan zhongyi <zh...@gmail.com>.
Hi，James，
What is the status of the release note now？
Thanks
发件人: tan zhongyi <je...@apache.org>
日期: 2019年6月28日 星期五 下午5:09
收件人: JiashunZhu <zh...@gmail.com>, "Wang,Weibing" <wa...@baidu.com>, "jamesge@apache.org" <ja...@apache.org>, "Hu,Wenwei" <hu...@baidu.com>
抄送: "dev@brpc.apache.org" <de...@brpc.apache.org>
主题: Re: Update for tasklist that needed for the first apache release and target timeline
Thanks jiashun & weibing，
We have made a big progress toward our first apache release.
@jamesge@apache.org<ma...@apache.org>, @Hu,Wenwei<ma...@baidu.com>, how about your task?
Thanks
发件人: JiashunZhu <zh...@gmail.com>
日期: 2019年6月28日 星期五 下午5:07
收件人: "Wang,Weibing" <wa...@baidu.com>
抄送: tan zhongyi <zh...@gmail.com>, "dev@brpc.apache.org" <de...@brpc.apache.org>, "Hu,Wenwei" <hu...@baidu.com>, "jamesge@apache.org" <ja...@apache.org>
主题: Re: Update for tasklist that needed for the first apache release and target timeline
1. check all third-party dependency including removed ,and update License if needed @JiashunZhu
done.
Wang,Weibing <wa...@baidu.com>> 于2019年6月28日周五 下午4:42写道：
2. Make a short License Header and add to all source code @Wang,Weibing
This is done.
Thanks.
在 2019/6/19 12:35，“tan zhongyi”<zh...@gmail.com>> 写入:
Hi， all，
Please update your working status by reply this email，
Thanks
It seems that jiashun has got big progress.
在 2019/6/6 下午3:06，“tan zhongyi”<je...@apache.org>> 写入:
Hi， guys，
Talked with gejun & jiashun，
Let's resign task for our first release， and our target release date is the end of June.
1. check all third-party dependency including removed ,and update License if needed @JiashunZhu
2. Make a short License Header and add to all source code @Wang,Weibing
3. Check if it can be build on mac and update readme to add "how to build" @Hu,Wenwei
4. Add Release note for this release @jamesge@apache.org<ma...@apache.org>
Let us move , the deadline will be the end of this Month.
And we will have a forum on Shanghai Next Month.
Thanks
--
Jiashun Zhu
Re: Update for tasklist that needed for the first apache release and
target timeline
Posted by tan zhongyi <zh...@gmail.com>.
Thanks jiashun & weibing，
We have made a big progress toward our first apache release.
@jamesge@apache.org<ma...@apache.org>, @Hu,Wenwei<ma...@baidu.com>, how about your task?
Thanks
发件人: JiashunZhu <zh...@gmail.com>
日期: 2019年6月28日 星期五 下午5:07
收件人: "Wang,Weibing" <wa...@baidu.com>
抄送: tan zhongyi <zh...@gmail.com>, "dev@brpc.apache.org" <de...@brpc.apache.org>, "Hu,Wenwei" <hu...@baidu.com>, "jamesge@apache.org" <ja...@apache.org>
主题: Re: Update for tasklist that needed for the first apache release and target timeline
1. check all third-party dependency including removed ,and update License if needed @JiashunZhu
done.
Wang,Weibing <wa...@baidu.com>> 于2019年6月28日周五 下午4:42写道：
2. Make a short License Header and add to all source code @Wang,Weibing
This is done.
Thanks.
在 2019/6/19 12:35，“tan zhongyi”<zh...@gmail.com>> 写入:
Hi， all，
Please update your working status by reply this email，
Thanks
It seems that jiashun has got big progress.
在 2019/6/6 下午3:06，“tan zhongyi”<je...@apache.org>> 写入:
Hi， guys，
Talked with gejun & jiashun，
Let's resign task for our first release， and our target release date is the end of June.
1. check all third-party dependency including removed ,and update License if needed @JiashunZhu
2. Make a short License Header and add to all source code @Wang,Weibing
3. Check if it can be build on mac and update readme to add "how to build" @Hu,Wenwei
4. Add Release note for this release @jamesge@apache.org<ma...@apache.org>
Let us move , the deadline will be the end of this Month.
And we will have a forum on Shanghai Next Month.
Thanks
--
Jiashun Zhu
Re: Update for tasklist that needed for the first apache release and
target timeline
Posted by JiashunZhu <zh...@gmail.com>.
1. check all third-party dependency including removed ,and update License
if needed @JiashunZhu
done.
Wang,Weibing <wa...@baidu.com> 于2019年6月28日周五 下午4:42写道：
> 2. Make a short License Header and add to all source code
> @Wang,Weibing
>
> This is done.
>
>
> Thanks.
>
> 在 2019/6/19 12:35，“tan zhongyi”<zh...@gmail.com> 写入:
>
> Hi， all，
> Please update your working status by reply this email，
> Thanks
>
> It seems that jiashun has got big progress.
>
>
> 在 2019/6/6 下午3:06，“tan zhongyi”<je...@apache.org> 写入:
>
> Hi， guys，
>
> Talked with gejun & jiashun，
> Let's resign task for our first release， and our target release
> date is the end of June.
> 1. check all third-party dependency including removed ,and update
> License if needed @JiashunZhu
> 2. Make a short License Header and add to all source code
> @Wang,Weibing
> 3. Check if it can be build on mac and update readme to add "how
> to build" @Hu,Wenwei
> 4. Add Release note for this release
> @jamesge@apache.org
>
> Let us move , the deadline will be the end of this Month.
> And we will have a forum on Shanghai Next Month.
>
> Thanks
>
>
>
>
>
>
>
--
Jiashun Zhu
Re: Update for tasklist that needed for the first apache release and
target timeline
Posted by "Wang,Weibing" <wa...@baidu.com>.
2. Make a short License Header and add to all source code @Wang,Weibing
This is done.
Thanks.
在 2019/6/19 12:35，“tan zhongyi”<zh...@gmail.com> 写入:
Hi， all，
Please update your working status by reply this email，
Thanks
It seems that jiashun has got big progress.
在 2019/6/6 下午3:06，“tan zhongyi”<je...@apache.org> 写入:
Hi， guys，
Talked with gejun & jiashun，
Let's resign task for our first release， and our target release date is the end of June.
1. check all third-party dependency including removed ,and update License if needed @JiashunZhu
2. Make a short License Header and add to all source code @Wang,Weibing
3. Check if it can be build on mac and update readme to add "how to build" @Hu,Wenwei
4. Add Release note for this release @jamesge@apache.org
Let us move , the deadline will be the end of this Month.
And we will have a forum on Shanghai Next Month.
Thanks
Re: Update for tasklist that needed for the first apache release and
target timeline
Posted by tan zhongyi <zh...@gmail.com>.
Hi， all，
Please update your working status by reply this email，
Thanks
It seems that jiashun has got big progress.
在 2019/6/6 下午3:06，“tan zhongyi”<je...@apache.org> 写入:
Hi， guys，
Talked with gejun & jiashun，
Let's resign task for our first release， and our target release date is the end of June.
1. check all third-party dependency including removed ,and update License if needed @JiashunZhu
2. Make a short License Header and add to all source code @Wang,Weibing
3. Check if it can be build on mac and update readme to add "how to build" @Hu,Wenwei
4. Add Release note for this release @jamesge@apache.org
Let us move , the deadline will be the end of this Month.
And we will have a forum on Shanghai Next Month.
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@brpc.apache.org
For additional commands, e-mail: dev-help@brpc.apache.org
Re: Update for tasklist that needed for the first apache release and
target timeline
Posted by tan zhongyi <zh...@gmail.com>.
Thanks， this task should be marked as completed， right？
James？
在 2019/6/10 下午5:57，“Hu,Wenwei”<hu...@baidu.com> 写入:
3. Check if it can be build on mac and update readme to add "how to build" @Hu,Wenwei
-------------------
I have updated the pull request for this task.
Thanks
在 2019/6/6 下午3:06，“tan zhongyi”<zh...@gmail.com> 写入:
Hi， guys，
Talked with gejun & jiashun，
Let's resign task for our first release， and our target release date is the end of June.
1. check all third-party dependency including removed ,and update License if needed @JiashunZhu
2. Make a short License Header and add to all source code @Wang,Weibing
3. Check if it can be build on mac and update readme to add "how to build" @Hu,Wenwei
4. Add Release note for this release @jamesge@apache.org
Let us move , the deadline will be the end of this Month.
And we will have a forum on Shanghai Next Month.
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@brpc.apache.org
For additional commands, e-mail: dev-help@brpc.apache.org
Re: Update for tasklist that needed for the first apache release and
target timeline
Posted by "Hu,Wenwei" <hu...@baidu.com>.
This pull request has been merged into master.
Thanks
Wenwei
在 2019/6/10 下午5:57，“Hu,Wenwei”<hu...@baidu.com> 写入:
3. Check if it can be build on mac and update readme to add "how to build" @Hu,Wenwei
-------------------
I have updated the pull request for this task.
Thanks
在 2019/6/6 下午3:06，“tan zhongyi”<zh...@gmail.com> 写入:
Hi， guys，
Talked with gejun & jiashun，
Let's resign task for our first release， and our target release date is the end of June.
1. check all third-party dependency including removed ,and update License if needed @JiashunZhu
2. Make a short License Header and add to all source code @Wang,Weibing
3. Check if it can be build on mac and update readme to add "how to build" @Hu,Wenwei
4. Add Release note for this release @jamesge@apache.org
Let us move , the deadline will be the end of this Month.
And we will have a forum on Shanghai Next Month.
Thanks
Re: Update for tasklist that needed for the first apache release and
target timeline
Posted by "Hu,Wenwei" <hu...@baidu.com>.
3. Check if it can be build on mac and update readme to add "how to build" @Hu,Wenwei
-------------------
I have updated the pull request for this task.
Thanks
在 2019/6/6 下午3:06，“tan zhongyi”<zh...@gmail.com> 写入:
Hi， guys，
Talked with gejun & jiashun，
Let's resign task for our first release， and our target release date is the end of June.
1. check all third-party dependency including removed ,and update License if needed @JiashunZhu
2. Make a short License Header and add to all source code @Wang,Weibing
3. Check if it can be build on mac and update readme to add "how to build" @Hu,Wenwei
4. Add Release note for this release @jamesge@apache.org
Let us move , the deadline will be the end of this Month.
And we will have a forum on Shanghai Next Month.
Thanks
Update for tasklist that needed for the first apache release and
target timeline
Posted by tan zhongyi <zh...@gmail.com>.
Hi， guys，
Talked with gejun & jiashun，
Let's resign task for our first release， and our target release date is the end of June.
1. check all third-party dependency including removed ,and update License if needed @JiashunZhu
2. Make a short License Header and add to all source code @Wang,Weibing
3. Check if it can be build on mac and update readme to add "how to build" @Hu,Wenwei
4. Add Release note for this release @jamesge@apache.org
Let us move , the deadline will be the end of this Month.
And we will have a forum on Shanghai Next Month.
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@brpc.apache.org
For additional commands, e-mail: dev-help@brpc.apache.org
Re: the tasklist that needed for the first apache release
Posted by tan zhongyi <zh...@gmail.com>.
Hi， @ Zhangyi Chen @ wang weibing @ James Ge @ huwenwei
any update on your tasks for first apache release?
If you have met some problem, please raise it here.
Thanks
在 2019/4/19 下午3:29，“tan zhongyi”<je...@apache.org> 写入:
Hi， guys，
Any update for your task?
@ Zhangyi Chen @ wang weibing @ James Ge @ huwenwei
Thanks
在 2019/4/9 上午8:45，“tan zhongyi”<je...@apache.org> 写入:
OK, let me push us to work on our tasks.
在 2019/3/29 下午4:07，“tan zhongyi”<je...@apache.org> 写入:
Great，thanks huwenwei.
Now Let me to clarify the task of our first release
1. Get all dependency third party’s copyright and apppend them to brpc License file
@ Zhangyi Chen
Hi, zhangyi，this task is the most difficult work for this release
You need to add every needed third party copyright into our's LICENSE file.
If you have any problem, please let us know, we will help on that
2. Add Notice and Disclaimer file to mention its copyright belong to apache foundation
@tanzhongyi already checked in, marked as done
3. Make a short license header, and add the header to all source files, including .h, .cpp, .java, etc
@wang weibing
Hi, weibing, would you please make a short license header for us to review first?
thanks
4. Check the source tarball to make sure it does not contain binary files except for data
@TanZhongyi pending
5. Prepare release note to list all import checkin and features
@James Ge ?
Hi, james, any progress?
6. Update Readme to add one section as “How to build”
@ huwenwei
Hi, huwenwei, any progress?
We can start to work now, and discuss related issues in this mail list to keep a good record.
Thanks
The most difficult part is #1, we need to list all third party code into brpc's License file,
If not permitted, we need to find another solution.
在 2019/3/29 下午2:41，“Hu,Wenwei”<hu...@baidu.com> 写入:
I would like take 6.
在 2019/3/28 09:23，“tan zhongyi”<zh...@gmail.com> 写入:
Thanks，zhangyi，
Anyone else who want to volunteer to take some task？
在 2019/3/27 下午10:17，“Zhangyi Chen”<fr...@gmail.com> 写入:
I would like take 1 and 2.
On Tue, Mar 26, 2019 at 2:25 PM tan zhongyi <zh...@gmail.com> wrote:
> Hi， all，
>
> We need to assign task for our first release .
> Anyone who volunteer to take ?
> Here is the task list, you can reply with it with your interested task,
> Thanks
>
>
> Here is the task list：
> 1. Get all dependency third party’s copyright and
> apppend them to brpc License file
>
> 2. Add Notice and Disclaimer file to mention its copyright
> belong to apache foundation
>
> 3. Make a short license header, and add the header to all
> source files, including .h, .cpp, .java, etc
>
> 4. Check the source tarball to make sure it does not contain
> binary files except for data
>
> 5. Prepare release note to list all import checkin and features
>
> 6. Update Readme to add one section as “How to build”
>
>
> BTW：Here is one important things about include third party code:
> From its website https://apache.org/legal/resolved.html
> CATEGORY X: WHAT CAN WE NOT INCLUDE IN AN ASF PROJECT?¶
> Apache project forbid some third party software in it, it includes:
> 1. AGPL， LGPL，GPL
> 2. BSD + Fackbook patient
> 3.BSD-4-clouse
>
>
>
>
> 在 2019/3/19 下午3:04，“tan zhongyi”<je...@apache.org> 写入:
>
> Here is one example from Doris's RD
> Doris just released its first apache version,
> The owner write a document step by step, very details
>
> Here it is :
> http://doris.apache.org/policy/release_process.html
>
>
>
>
>
> 在 2019/3/18 下午11:26，“tan zhongyi”<zh...@gmail.com> 写入:
>
> Hi， guys,
>
> We need to release our first apache release for brpc in Q2.
>
> And it will be a great step to be an TOP level apache project for
> brpc.
>
> Here is some tasks that need to be done for the release after I
> refer to document from apache.org
>
>
> 1. Get all dependency third party’s copyright and apppend them
> to brpc License file
>
> 2. Add Notice and Disclaimer file to mention its copyright
> belong to apache foundation
>
> 3. Make a short license header, and add the header to all
> source files, including .h, .cpp, .java, etc
>
> 4. Check the source tarball to make sure it does not contain
> binary files except for data
>
> 5. Prepare release note to list all import checkin and features
>
> 6. Update Readme to add one section as “How to build”
>
>
>
>
> When we finish these tasks, then we need to open a thread to vote
> on dev@brpc.apache.org<ma...@brpc.apache.org>,
> If got approved, we need to open another vote on incubator mail
> list.
> If not approved, we should make changes according to our mentor
> or other’s suggestion, and vote again.
>
> I remember that it is very common to have several vote for the
> first release.
>
> That’s all for a release, anyone have comments?
> Thanks
>
>
>
>
?B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�?�?[��X��ܚX�K??K[XZ[?�??]�][��X��ܚX�P?��?˘\?X�?K�ܙ�B��܈?Y??]?[ۘ[??��[X[�?�??K[XZ[?�??]�Z?[???��?˘\?X�?K�ܙ�B
B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�� [��X��ܚX�KK[XZ[
�]�][��X��ܚX�P��˘\X�K�ܙ�B��܈Y][ۘ[��[X[� �K[XZ[
�]�Z[ ��˘\X�K�ܙ�B
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@brpc.apache.org
For additional commands, e-mail: dev-help@brpc.apache.org
Re: the tasklist that needed for the first apache release
Posted by tan zhongyi <zh...@gmail.com>.
Hi， guys，
Any update for your task?
@ Zhangyi Chen @ wang weibing @ James Ge @ huwenwei
Thanks
在 2019/4/9 上午8:45，“tan zhongyi”<je...@apache.org> 写入:
OK, let me push us to work on our tasks.
在 2019/3/29 下午4:07，“tan zhongyi”<je...@apache.org> 写入:
Great，thanks huwenwei.
Now Let me to clarify the task of our first release
1. Get all dependency third party’s copyright and apppend them to brpc License file
@ Zhangyi Chen
Hi, zhangyi，this task is the most difficult work for this release
You need to add every needed third party copyright into our's LICENSE file.
If you have any problem, please let us know, we will help on that
2. Add Notice and Disclaimer file to mention its copyright belong to apache foundation
@tanzhongyi already checked in, marked as done
3. Make a short license header, and add the header to all source files, including .h, .cpp, .java, etc
@wang weibing
Hi, weibing, would you please make a short license header for us to review first?
thanks
4. Check the source tarball to make sure it does not contain binary files except for data
@TanZhongyi pending
5. Prepare release note to list all import checkin and features
@James Ge ?
Hi, james, any progress?
6. Update Readme to add one section as “How to build”
@ huwenwei
Hi, huwenwei, any progress?
We can start to work now, and discuss related issues in this mail list to keep a good record.
Thanks
The most difficult part is #1, we need to list all third party code into brpc's License file,
If not permitted, we need to find another solution.
在 2019/3/29 下午2:41，“Hu,Wenwei”<hu...@baidu.com> 写入:
I would like take 6.
在 2019/3/28 09:23，“tan zhongyi”<zh...@gmail.com> 写入:
Thanks，zhangyi，
Anyone else who want to volunteer to take some task？
在 2019/3/27 下午10:17，“Zhangyi Chen”<fr...@gmail.com> 写入:
I would like take 1 and 2.
On Tue, Mar 26, 2019 at 2:25 PM tan zhongyi <zh...@gmail.com> wrote:
> Hi， all，
>
> We need to assign task for our first release .
> Anyone who volunteer to take ?
> Here is the task list, you can reply with it with your interested task,
> Thanks
>
>
> Here is the task list：
> 1. Get all dependency third party’s copyright and
> apppend them to brpc License file
>
> 2. Add Notice and Disclaimer file to mention its copyright
> belong to apache foundation
>
> 3. Make a short license header, and add the header to all
> source files, including .h, .cpp, .java, etc
>
> 4. Check the source tarball to make sure it does not contain
> binary files except for data
>
> 5. Prepare release note to list all import checkin and features
>
> 6. Update Readme to add one section as “How to build”
>
>
> BTW：Here is one important things about include third party code:
> From its website https://apache.org/legal/resolved.html
> CATEGORY X: WHAT CAN WE NOT INCLUDE IN AN ASF PROJECT?¶
> Apache project forbid some third party software in it, it includes:
> 1. AGPL， LGPL，GPL
> 2. BSD + Fackbook patient
> 3.BSD-4-clouse
>
>
>
>
> 在 2019/3/19 下午3:04，“tan zhongyi”<je...@apache.org> 写入:
>
> Here is one example from Doris's RD
> Doris just released its first apache version,
> The owner write a document step by step, very details
>
> Here it is :
> http://doris.apache.org/policy/release_process.html
>
>
>
>
>
> 在 2019/3/18 下午11:26，“tan zhongyi”<zh...@gmail.com> 写入:
>
> Hi， guys,
>
> We need to release our first apache release for brpc in Q2.
>
> And it will be a great step to be an TOP level apache project for
> brpc.
>
> Here is some tasks that need to be done for the release after I
> refer to document from apache.org
>
>
> 1. Get all dependency third party’s copyright and apppend them
> to brpc License file
>
> 2. Add Notice and Disclaimer file to mention its copyright
> belong to apache foundation
>
> 3. Make a short license header, and add the header to all
> source files, including .h, .cpp, .java, etc
>
> 4. Check the source tarball to make sure it does not contain
> binary files except for data
>
> 5. Prepare release note to list all import checkin and features
>
> 6. Update Readme to add one section as “How to build”
>
>
>
>
> When we finish these tasks, then we need to open a thread to vote
> on dev@brpc.apache.org<ma...@brpc.apache.org>,
> If got approved, we need to open another vote on incubator mail
> list.
> If not approved, we should make changes according to our mentor
> or other’s suggestion, and vote again.
>
> I remember that it is very common to have several vote for the
> first release.
>
> That’s all for a release, anyone have comments?
> Thanks
>
>
>
>
?B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�?�?[��X��ܚX�K??K[XZ[?�??]�][��X��ܚX�P?��?˘\?X�?K�ܙ�B��܈?Y??]?[ۘ[??��[X[�?�??K[XZ[?�??]�Z?[???��?˘\?X�?K�ܙ�B
B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�� [��X��ܚX�KK[XZ[
�]�][��X��ܚX�P��˘\X�K�ܙ�B��܈Y][ۘ[��[X[� �K[XZ[
�]�Z[ ��˘\X�K�ܙ�B
Re: the tasklist that needed for the first apache release
Posted by tan zhongyi <zh...@gmail.com>.
OK, let me push us to work on our tasks.
在 2019/3/29 下午4:07，“tan zhongyi”<je...@apache.org> 写入:
Great，thanks huwenwei.
Now Let me to clarify the task of our first release
1. Get all dependency third party’s copyright and apppend them to brpc License file
@ Zhangyi Chen
Hi, zhangyi，this task is the most difficult work for this release
You need to add every needed third party copyright into our's LICENSE file.
If you have any problem, please let us know, we will help on that
2. Add Notice and Disclaimer file to mention its copyright belong to apache foundation
@tanzhongyi already checked in, marked as done
3. Make a short license header, and add the header to all source files, including .h, .cpp, .java, etc
@wang weibing
Hi, weibing, would you please make a short license header for us to review first?
thanks
4. Check the source tarball to make sure it does not contain binary files except for data
@TanZhongyi pending
5. Prepare release note to list all import checkin and features
@James Ge ?
Hi, james, any progress?
6. Update Readme to add one section as “How to build”
@ huwenwei
Hi, huwenwei, any progress?
We can start to work now, and discuss related issues in this mail list to keep a good record.
Thanks
The most difficult part is #1, we need to list all third party code into brpc's License file,
If not permitted, we need to find another solution.
在 2019/3/29 下午2:41，“Hu,Wenwei”<hu...@baidu.com> 写入:
I would like take 6.
在 2019/3/28 09:23，“tan zhongyi”<zh...@gmail.com> 写入:
Thanks，zhangyi，
Anyone else who want to volunteer to take some task？
在 2019/3/27 下午10:17，“Zhangyi Chen”<fr...@gmail.com> 写入:
I would like take 1 and 2.
On Tue, Mar 26, 2019 at 2:25 PM tan zhongyi <zh...@gmail.com> wrote:
> Hi， all，
>
> We need to assign task for our first release .
> Anyone who volunteer to take ?
> Here is the task list, you can reply with it with your interested task,
> Thanks
>
>
> Here is the task list：
> 1. Get all dependency third party’s copyright and
> apppend them to brpc License file
>
> 2. Add Notice and Disclaimer file to mention its copyright
> belong to apache foundation
>
> 3. Make a short license header, and add the header to all
> source files, including .h, .cpp, .java, etc
>
> 4. Check the source tarball to make sure it does not contain
> binary files except for data
>
> 5. Prepare release note to list all import checkin and features
>
> 6. Update Readme to add one section as “How to build”
>
>
> BTW：Here is one important things about include third party code:
> From its website https://apache.org/legal/resolved.html
> CATEGORY X: WHAT CAN WE NOT INCLUDE IN AN ASF PROJECT?¶
> Apache project forbid some third party software in it, it includes:
> 1. AGPL， LGPL，GPL
> 2. BSD + Fackbook patient
> 3.BSD-4-clouse
>
>
>
>
> 在 2019/3/19 下午3:04，“tan zhongyi”<je...@apache.org> 写入:
>
> Here is one example from Doris's RD
> Doris just released its first apache version,
> The owner write a document step by step, very details
>
> Here it is :
> http://doris.apache.org/policy/release_process.html
>
>
>
>
>
> 在 2019/3/18 下午11:26，“tan zhongyi”<zh...@gmail.com> 写入:
>
> Hi， guys,
>
> We need to release our first apache release for brpc in Q2.
>
> And it will be a great step to be an TOP level apache project for
> brpc.
>
> Here is some tasks that need to be done for the release after I
> refer to document from apache.org
>
>
> 1. Get all dependency third party’s copyright and apppend them
> to brpc License file
>
> 2. Add Notice and Disclaimer file to mention its copyright
> belong to apache foundation
>
> 3. Make a short license header, and add the header to all
> source files, including .h, .cpp, .java, etc
>
> 4. Check the source tarball to make sure it does not contain
> binary files except for data
>
> 5. Prepare release note to list all import checkin and features
>
> 6. Update Readme to add one section as “How to build”
>
>
>
>
> When we finish these tasks, then we need to open a thread to vote
> on dev@brpc.apache.org<ma...@brpc.apache.org>,
> If got approved, we need to open another vote on incubator mail
> list.
> If not approved, we should make changes according to our mentor
> or other’s suggestion, and vote again.
>
> I remember that it is very common to have several vote for the
> first release.
>
> That’s all for a release, anyone have comments?
> Thanks
>
>
>
>
?B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�?�?[��X��ܚX�K??K[XZ[?�??]�][��X��ܚX�P?��?˘\?X�?K�ܙ�B��܈?Y??]?[ۘ[??��[X[�?�??K[XZ[?�??]�Z?[???��?˘\?X�?K�ܙ�B
B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�� [��X��ܚX�KK[XZ[
�]�][��X��ܚX�P��˘\X�K�ܙ�B��܈Y][ۘ[��[X[� �K[XZ[
�]�Z[ ��˘\X�K�ܙ�B
Re: the tasklist that needed for the first apache release
Posted by James Ge <jg...@gmail.com>.
ok, I'll take task 5
On Fri, Mar 29, 2019 at 4:07 PM tan zhongyi <zh...@gmail.com> wrote:
> Great，thanks huwenwei.
>
> Now Let me to clarify the task of our first release
>
> 1. Get all dependency third party’s copyright and apppend them to brpc
> License file
> @ Zhangyi Chen
>
> 2. Add Notice and Disclaimer file to mention its copyright belong to
> apache foundation
> @tanzhongyi
>
> 3. Make a short license header, and add the header to all source files,
> including .h, .cpp, .java, etc
> @wang weibing
>
> 4. Check the source tarball to make sure it does not contain binary files
> except for data
> @TanZhongyi
>
> 5. Prepare release note to list all import checkin and features
> @James Ge ?
> Gejun, can you do that?
>
> 6. Update Readme to add one section as “How to build”
> @ huwenwei
>
> We can start to work now, and discuss related issues in this mail list to
> keep a good record.
> Thanks
>
> The most difficult part is #1, we need to list all third party code into
> brpc's License file,
> If not permitted, we need to find another solution.
>
>
>
> 在 2019/3/29 下午2:41，“Hu,Wenwei”<hu...@baidu.com> 写入:
>
> I would like take 6.
>
>
>
> 在 2019/3/28 09:23，“tan zhongyi”<zh...@gmail.com> 写入:
>
> Thanks，zhangyi，
>
> Anyone else who want to volunteer to take some task？
>
> 在 2019/3/27 下午10:17，“Zhangyi Chen”<fr...@gmail.com> 写入:
>
> I would like take 1 and 2.
>
> On Tue, Mar 26, 2019 at 2:25 PM tan zhongyi <
> zhongyi.tan@gmail.com> wrote:
>
> > Hi， all，
> >
> > We need to assign task for our first release .
> > Anyone who volunteer to take ?
> > Here is the task list, you can reply with it with your
> interested task,
> > Thanks
> >
> >
> > Here is the task list：
> > 1. Get all dependency third party’s
> copyright and
> > apppend them to brpc License file
> >
> > 2. Add Notice and Disclaimer file to mention its
> copyright
> > belong to apache foundation
> >
> > 3. Make a short license header, and add the
> header to all
> > source files, including .h, .cpp, .java, etc
> >
> > 4. Check the source tarball to make sure it does
> not contain
> > binary files except for data
> >
> > 5. Prepare release note to list all import
> checkin and features
> >
> > 6. Update Readme to add one section as “How to
> build”
> >
> >
> > BTW：Here is one important things about include third party
> code:
> > From its website https://apache.org/legal/resolved.html
> > CATEGORY X: WHAT CAN WE NOT INCLUDE IN AN ASF PROJECT?¶
> > Apache project forbid some third party software in it,
> it includes:
> > 1. AGPL， LGPL，GPL
> > 2. BSD + Fackbook patient
> > 3.BSD-4-clouse
> >
> >
> >
> >
> > 在 2019/3/19 下午3:04，“tan zhongyi”<je...@apache.org> 写入:
> >
> > Here is one example from Doris's RD
> > Doris just released its first apache version,
> > The owner write a document step by step, very details
> >
> > Here it is :
> > http://doris.apache.org/policy/release_process.html
> >
> >
> >
> >
> >
> > 在 2019/3/18 下午11:26，“tan zhongyi”<zh...@gmail.com>
> 写入:
> >
> > Hi， guys,
> >
> > We need to release our first apache release for
> brpc in Q2.
> >
> > And it will be a great step to be an TOP level
> apache project for
> > brpc.
> >
> > Here is some tasks that need to be done for the
> release after I
> > refer to document from apache.org
> >
> >
> > 1. Get all dependency third party’s copyright
> and apppend them
> > to brpc License file
> >
> > 2. Add Notice and Disclaimer file to mention its
> copyright
> > belong to apache foundation
> >
> > 3. Make a short license header, and add the
> header to all
> > source files, including .h, .cpp, .java, etc
> >
> > 4. Check the source tarball to make sure it does
> not contain
> > binary files except for data
> >
> > 5. Prepare release note to list all import
> checkin and features
> >
> > 6. Update Readme to add one section as “How to
> build”
> >
> >
> >
> >
> > When we finish these tasks, then we need to open a
> thread to vote
> > on dev@brpc.apache.org<ma...@brpc.apache.org>,
> > If got approved, we need to open another vote on
> incubator mail
> > list.
> > If not approved, we should make changes according
> to our mentor
> > or other’s suggestion, and vote again.
> >
> > I remember that it is very common to have several
> vote for the
> > first release.
> >
> > That’s all for a release, anyone have comments?
> > Thanks
> >
> >
> >
> >
>
>
> ?B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�?�?[��X��ܚX�K??K[XZ[?�??]�][��X��ܚX�P?��?˘\?X�?K�ܙ�B��܈?Y??]?[ۘ[??��[X[�?�??K[XZ[?�??]�Z?[???��?˘\?X�?K�ܙ�B
>
>
> B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�
> � [��X��ܚX�K K[XZ[
> � ]�][��X��ܚX�P �� ˘\ X� K�ܙ�B��܈ Y ] [ۘ[ ��[X[� � K[XZ[
> � ]�Z [ �� ˘\ X� K�ܙ�B
>
Re: the tasklist that needed for the first apache release
Posted by tan zhongyi <zh...@gmail.com>.
Hi, I have created one pull request to add NOTICE.txt
https://github.com/apache/incubator-brpc/pull/710
please take a look,thanks
here is the content:
Apache brpc (incubating)
Copyright 2019 The Apache Software Foundation
This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).
Based on source code originally developed by
Baidu (http://www.baidu.com/).
在 2019/3/29 下午4:07，“tan zhongyi”<je...@apache.org> 写入:
Great，thanks huwenwei.
Now Let me to clarify the task of our first release
1. Get all dependency third party’s copyright and apppend them to brpc License file
@ Zhangyi Chen
2. Add Notice and Disclaimer file to mention its copyright belong to apache foundation
@tanzhongyi
3. Make a short license header, and add the header to all source files, including .h, .cpp, .java, etc
@wang weibing
4. Check the source tarball to make sure it does not contain binary files except for data
@TanZhongyi
5. Prepare release note to list all import checkin and features
@James Ge ?
Gejun, can you do that?
6. Update Readme to add one section as “How to build”
@ huwenwei
We can start to work now, and discuss related issues in this mail list to keep a good record.
Thanks
The most difficult part is #1, we need to list all third party code into brpc's License file,
If not permitted, we need to find another solution.
在 2019/3/29 下午2:41，“Hu,Wenwei”<hu...@baidu.com> 写入:
I would like take 6.
在 2019/3/28 09:23，“tan zhongyi”<zh...@gmail.com> 写入:
Thanks，zhangyi，
Anyone else who want to volunteer to take some task？
在 2019/3/27 下午10:17，“Zhangyi Chen”<fr...@gmail.com> 写入:
I would like take 1 and 2.
On Tue, Mar 26, 2019 at 2:25 PM tan zhongyi <zh...@gmail.com> wrote:
> Hi， all，
>
> We need to assign task for our first release .
> Anyone who volunteer to take ?
> Here is the task list, you can reply with it with your interested task,
> Thanks
>
>
> Here is the task list：
> 1. Get all dependency third party’s copyright and
> apppend them to brpc License file
>
> 2. Add Notice and Disclaimer file to mention its copyright
> belong to apache foundation
>
> 3. Make a short license header, and add the header to all
> source files, including .h, .cpp, .java, etc
>
> 4. Check the source tarball to make sure it does not contain
> binary files except for data
>
> 5. Prepare release note to list all import checkin and features
>
> 6. Update Readme to add one section as “How to build”
>
>
> BTW：Here is one important things about include third party code:
> From its website https://apache.org/legal/resolved.html
> CATEGORY X: WHAT CAN WE NOT INCLUDE IN AN ASF PROJECT?¶
> Apache project forbid some third party software in it, it includes:
> 1. AGPL， LGPL，GPL
> 2. BSD + Fackbook patient
> 3.BSD-4-clouse
>
>
>
>
> 在 2019/3/19 下午3:04，“tan zhongyi”<je...@apache.org> 写入:
>
> Here is one example from Doris's RD
> Doris just released its first apache version,
> The owner write a document step by step, very details
>
> Here it is :
> http://doris.apache.org/policy/release_process.html
>
>
>
>
>
> 在 2019/3/18 下午11:26，“tan zhongyi”<zh...@gmail.com> 写入:
>
> Hi， guys,
>
> We need to release our first apache release for brpc in Q2.
>
> And it will be a great step to be an TOP level apache project for
> brpc.
>
> Here is some tasks that need to be done for the release after I
> refer to document from apache.org
>
>
> 1. Get all dependency third party’s copyright and apppend them
> to brpc License file
>
> 2. Add Notice and Disclaimer file to mention its copyright
> belong to apache foundation
>
> 3. Make a short license header, and add the header to all
> source files, including .h, .cpp, .java, etc
>
> 4. Check the source tarball to make sure it does not contain
> binary files except for data
>
> 5. Prepare release note to list all import checkin and features
>
> 6. Update Readme to add one section as “How to build”
>
>
>
>
> When we finish these tasks, then we need to open a thread to vote
> on dev@brpc.apache.org<ma...@brpc.apache.org>,
> If got approved, we need to open another vote on incubator mail
> list.
> If not approved, we should make changes according to our mentor
> or other’s suggestion, and vote again.
>
> I remember that it is very common to have several vote for the
> first release.
>
> That’s all for a release, anyone have comments?
> Thanks
>
>
>
>
?B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�?�?[��X��ܚX�K??K[XZ[?�??]�][��X��ܚX�P?��?˘\?X�?K�ܙ�B��܈?Y??]?[ۘ[??��[X[�?�??K[XZ[?�??]�Z?[???��?˘\?X�?K�ܙ�B
B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�� [��X��ܚX�KK[XZ[
�]�][��X��ܚX�P��˘\X�K�ܙ�B��܈Y][ۘ[��[X[� �K[XZ[
�]�Z[ ��˘\X�K�ܙ�B
Re: the tasklist that needed for the first apache release
Posted by tan zhongyi <zh...@gmail.com>.
Great，thanks huwenwei.
Now Let me to clarify the task of our first release
1. Get all dependency third party’s copyright and apppend them to brpc License file
@ Zhangyi Chen
2. Add Notice and Disclaimer file to mention its copyright belong to apache foundation
@tanzhongyi
3. Make a short license header, and add the header to all source files, including .h, .cpp, .java, etc
@wang weibing
4. Check the source tarball to make sure it does not contain binary files except for data
@TanZhongyi
5. Prepare release note to list all import checkin and features
@James Ge ?
Gejun, can you do that?
6. Update Readme to add one section as “How to build”
@ huwenwei
We can start to work now, and discuss related issues in this mail list to keep a good record.
Thanks
The most difficult part is #1, we need to list all third party code into brpc's License file,
If not permitted, we need to find another solution.
在 2019/3/29 下午2:41，“Hu,Wenwei”<hu...@baidu.com> 写入:
I would like take 6.
在 2019/3/28 09:23，“tan zhongyi”<zh...@gmail.com> 写入:
Thanks，zhangyi，
Anyone else who want to volunteer to take some task？
在 2019/3/27 下午10:17，“Zhangyi Chen”<fr...@gmail.com> 写入:
I would like take 1 and 2.
On Tue, Mar 26, 2019 at 2:25 PM tan zhongyi <zh...@gmail.com> wrote:
> Hi， all，
>
> We need to assign task for our first release .
> Anyone who volunteer to take ?
> Here is the task list, you can reply with it with your interested task,
> Thanks
>
>
> Here is the task list：
> 1. Get all dependency third party’s copyright and
> apppend them to brpc License file
>
> 2. Add Notice and Disclaimer file to mention its copyright
> belong to apache foundation
>
> 3. Make a short license header, and add the header to all
> source files, including .h, .cpp, .java, etc
>
> 4. Check the source tarball to make sure it does not contain
> binary files except for data
>
> 5. Prepare release note to list all import checkin and features
>
> 6. Update Readme to add one section as “How to build”
>
>
> BTW：Here is one important things about include third party code:
> From its website https://apache.org/legal/resolved.html
> CATEGORY X: WHAT CAN WE NOT INCLUDE IN AN ASF PROJECT?¶
> Apache project forbid some third party software in it, it includes:
> 1. AGPL， LGPL，GPL
> 2. BSD + Fackbook patient
> 3.BSD-4-clouse
>
>
>
>
> 在 2019/3/19 下午3:04，“tan zhongyi”<je...@apache.org> 写入:
>
> Here is one example from Doris's RD
> Doris just released its first apache version,
> The owner write a document step by step, very details
>
> Here it is :
> http://doris.apache.org/policy/release_process.html
>
>
>
>
>
> 在 2019/3/18 下午11:26，“tan zhongyi”<zh...@gmail.com> 写入:
>
> Hi， guys,
>
> We need to release our first apache release for brpc in Q2.
>
> And it will be a great step to be an TOP level apache project for
> brpc.
>
> Here is some tasks that need to be done for the release after I
> refer to document from apache.org
>
>
> 1. Get all dependency third party’s copyright and apppend them
> to brpc License file
>
> 2. Add Notice and Disclaimer file to mention its copyright
> belong to apache foundation
>
> 3. Make a short license header, and add the header to all
> source files, including .h, .cpp, .java, etc
>
> 4. Check the source tarball to make sure it does not contain
> binary files except for data
>
> 5. Prepare release note to list all import checkin and features
>
> 6. Update Readme to add one section as “How to build”
>
>
>
>
> When we finish these tasks, then we need to open a thread to vote
> on dev@brpc.apache.org<ma...@brpc.apache.org>,
> If got approved, we need to open another vote on incubator mail
> list.
> If not approved, we should make changes according to our mentor
> or other’s suggestion, and vote again.
>
> I remember that it is very common to have several vote for the
> first release.
>
> That’s all for a release, anyone have comments?
> Thanks
>
>
>
>
?B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�?�?[��X��ܚX�K??K[XZ[?�??]�][��X��ܚX�P?��?˘\?X�?K�ܙ�B��܈?Y??]?[ۘ[??��[X[�?�??K[XZ[?�??]�Z?[???��?˘\?X�?K�ܙ�B
B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�� [��X��ܚX�KK[XZ[
�]�][��X��ܚX�P��˘\X�K�ܙ�B��܈Y][ۘ[��[X[� �K[XZ[
�]�Z[ ��˘\X�K�ܙ�B
Re: the tasklist that needed for the first apache release
Posted by "Hu,Wenwei" <hu...@baidu.com>.
I would like take 6.
在 2019/3/28 09:23，“tan zhongyi”<zh...@gmail.com> 写入:
Thanks，zhangyi，
Anyone else who want to volunteer to take some task？
在 2019/3/27 下午10:17，“Zhangyi Chen”<fr...@gmail.com> 写入:
I would like take 1 and 2.
On Tue, Mar 26, 2019 at 2:25 PM tan zhongyi <zh...@gmail.com> wrote:
> Hi， all，
>
> We need to assign task for our first release .
> Anyone who volunteer to take ?
> Here is the task list, you can reply with it with your interested task,
> Thanks
>
>
> Here is the task list：
> 1. Get all dependency third party’s copyright and
> apppend them to brpc License file
>
> 2. Add Notice and Disclaimer file to mention its copyright
> belong to apache foundation
>
> 3. Make a short license header, and add the header to all
> source files, including .h, .cpp, .java, etc
>
> 4. Check the source tarball to make sure it does not contain
> binary files except for data
>
> 5. Prepare release note to list all import checkin and features
>
> 6. Update Readme to add one section as “How to build”
>
>
> BTW：Here is one important things about include third party code:
> From its website https://apache.org/legal/resolved.html
> CATEGORY X: WHAT CAN WE NOT INCLUDE IN AN ASF PROJECT?¶
> Apache project forbid some third party software in it, it includes:
> 1. AGPL， LGPL，GPL
> 2. BSD + Fackbook patient
> 3.BSD-4-clouse
>
>
>
>
> 在 2019/3/19 下午3:04，“tan zhongyi”<je...@apache.org> 写入:
>
> Here is one example from Doris's RD
> Doris just released its first apache version,
> The owner write a document step by step, very details
>
> Here it is :
> http://doris.apache.org/policy/release_process.html
>
>
>
>
>
> 在 2019/3/18 下午11:26，“tan zhongyi”<zh...@gmail.com> 写入:
>
> Hi， guys,
>
> We need to release our first apache release for brpc in Q2.
>
> And it will be a great step to be an TOP level apache project for
> brpc.
>
> Here is some tasks that need to be done for the release after I
> refer to document from apache.org
>
>
> 1. Get all dependency third party’s copyright and apppend them
> to brpc License file
>
> 2. Add Notice and Disclaimer file to mention its copyright
> belong to apache foundation
>
> 3. Make a short license header, and add the header to all
> source files, including .h, .cpp, .java, etc
>
> 4. Check the source tarball to make sure it does not contain
> binary files except for data
>
> 5. Prepare release note to list all import checkin and features
>
> 6. Update Readme to add one section as “How to build”
>
>
>
>
> When we finish these tasks, then we need to open a thread to vote
> on dev@brpc.apache.org<ma...@brpc.apache.org>,
> If got approved, we need to open another vote on incubator mail
> list.
> If not approved, we should make changes according to our mentor
> or other’s suggestion, and vote again.
>
> I remember that it is very common to have several vote for the
> first release.
>
> That’s all for a release, anyone have comments?
> Thanks
>
>
>
>
?B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�?�?[��X��ܚX�K??K[XZ[?�??]�][��X��ܚX�P?��?˘\?X�?K�ܙ�B��܈?Y??]?[ۘ[??��[X[�?�??K[XZ[?�??]�Z?[???��?˘\?X�?K�ܙ�B
Re: the tasklist that needed for the first apache release
Posted by "Wang,Weibing" <wa...@baidu.com>.
I would like to take 3.
在 2019/3/28 09:23，“tan zhongyi”<zh...@gmail.com> 写入:
Thanks，zhangyi，
Anyone else who want to volunteer to take some task？
在 2019/3/27 下午10:17，“Zhangyi Chen”<fr...@gmail.com> 写入:
I would like take 1 and 2.
On Tue, Mar 26, 2019 at 2:25 PM tan zhongyi <zh...@gmail.com> wrote:
> Hi， all，
>
> We need to assign task for our first release .
> Anyone who volunteer to take ?
> Here is the task list, you can reply with it with your interested task,
> Thanks
>
>
> Here is the task list：
> 1. Get all dependency third party’s copyright and
> apppend them to brpc License file
>
> 2. Add Notice and Disclaimer file to mention its copyright
> belong to apache foundation
>
> 3. Make a short license header, and add the header to all
> source files, including .h, .cpp, .java, etc
>
> 4. Check the source tarball to make sure it does not contain
> binary files except for data
>
> 5. Prepare release note to list all import checkin and features
>
> 6. Update Readme to add one section as “How to build”
>
>
> BTW：Here is one important things about include third party code:
> From its website https://apache.org/legal/resolved.html
> CATEGORY X: WHAT CAN WE NOT INCLUDE IN AN ASF PROJECT?¶
> Apache project forbid some third party software in it, it includes:
> 1. AGPL， LGPL，GPL
> 2. BSD + Fackbook patient
> 3.BSD-4-clouse
>
>
>
>
> 在 2019/3/19 下午3:04，“tan zhongyi”<je...@apache.org> 写入:
>
> Here is one example from Doris's RD
> Doris just released its first apache version,
> The owner write a document step by step, very details
>
> Here it is :
> http://doris.apache.org/policy/release_process.html
>
>
>
>
>
> 在 2019/3/18 下午11:26，“tan zhongyi”<zh...@gmail.com> 写入:
>
> Hi， guys,
>
> We need to release our first apache release for brpc in Q2.
>
> And it will be a great step to be an TOP level apache project for
> brpc.
>
> Here is some tasks that need to be done for the release after I
> refer to document from apache.org
>
>
> 1. Get all dependency third party’s copyright and apppend them
> to brpc License file
>
> 2. Add Notice and Disclaimer file to mention its copyright
> belong to apache foundation
>
> 3. Make a short license header, and add the header to all
> source files, including .h, .cpp, .java, etc
>
> 4. Check the source tarball to make sure it does not contain
> binary files except for data
>
> 5. Prepare release note to list all import checkin and features
>
> 6. Update Readme to add one section as “How to build”
>
>
>
>
> When we finish these tasks, then we need to open a thread to vote
> on dev@brpc.apache.org<ma...@brpc.apache.org>,
> If got approved, we need to open another vote on incubator mail
> list.
> If not approved, we should make changes according to our mentor
> or other’s suggestion, and vote again.
>
> I remember that it is very common to have several vote for the
> first release.
>
> That’s all for a release, anyone have comments?
> Thanks
>
>
>
>
?B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�?�?[��X��ܚX�K??K[XZ[?�??]�][��X��ܚX�P?��?˘\?X�?K�ܙ�B��܈?Y??]?[ۘ[??��[X[�?�??K[XZ[?�??]�Z?[???��?˘\?X�?K�ܙ�B
Re: the tasklist that needed for the first apache release
Posted by tan zhongyi <zh...@gmail.com>.
Thanks，zhangyi，
Anyone else who want to volunteer to take some task？
在 2019/3/27 下午10:17，“Zhangyi Chen”<fr...@gmail.com> 写入:
I would like take 1 and 2.
On Tue, Mar 26, 2019 at 2:25 PM tan zhongyi <zh...@gmail.com> wrote:
> Hi， all，
>
> We need to assign task for our first release .
> Anyone who volunteer to take ?
> Here is the task list, you can reply with it with your interested task,
> Thanks
>
>
> Here is the task list：
> 1. Get all dependency third party’s copyright and
> apppend them to brpc License file
>
> 2. Add Notice and Disclaimer file to mention its copyright
> belong to apache foundation
>
> 3. Make a short license header, and add the header to all
> source files, including .h, .cpp, .java, etc
>
> 4. Check the source tarball to make sure it does not contain
> binary files except for data
>
> 5. Prepare release note to list all import checkin and features
>
> 6. Update Readme to add one section as “How to build”
>
>
> BTW：Here is one important things about include third party code:
> From its website https://apache.org/legal/resolved.html
> CATEGORY X: WHAT CAN WE NOT INCLUDE IN AN ASF PROJECT?¶
> Apache project forbid some third party software in it, it includes:
> 1. AGPL， LGPL，GPL
> 2. BSD + Fackbook patient
> 3.BSD-4-clouse
>
>
>
>
> 在 2019/3/19 下午3:04，“tan zhongyi”<je...@apache.org> 写入:
>
> Here is one example from Doris's RD
> Doris just released its first apache version,
> The owner write a document step by step, very details
>
> Here it is :
> http://doris.apache.org/policy/release_process.html
>
>
>
>
>
> 在 2019/3/18 下午11:26，“tan zhongyi”<zh...@gmail.com> 写入:
>
> Hi， guys,
>
> We need to release our first apache release for brpc in Q2.
>
> And it will be a great step to be an TOP level apache project for
> brpc.
>
> Here is some tasks that need to be done for the release after I
> refer to document from apache.org
>
>
> 1. Get all dependency third party’s copyright and apppend them
> to brpc License file
>
> 2. Add Notice and Disclaimer file to mention its copyright
> belong to apache foundation
>
> 3. Make a short license header, and add the header to all
> source files, including .h, .cpp, .java, etc
>
> 4. Check the source tarball to make sure it does not contain
> binary files except for data
>
> 5. Prepare release note to list all import checkin and features
>
> 6. Update Readme to add one section as “How to build”
>
>
>
>
> When we finish these tasks, then we need to open a thread to vote
> on dev@brpc.apache.org<ma...@brpc.apache.org>,
> If got approved, we need to open another vote on incubator mail
> list.
> If not approved, we should make changes according to our mentor
> or other’s suggestion, and vote again.
>
> I remember that it is very common to have several vote for the
> first release.
>
> That’s all for a release, anyone have comments?
> Thanks
>
>
>
>
Re: the tasklist that needed for the first apache release
Posted by Zhangyi Chen <fr...@gmail.com>.
I would like take 1 and 2.
On Tue, Mar 26, 2019 at 2:25 PM tan zhongyi <zh...@gmail.com> wrote:
> Hi， all，
>
> We need to assign task for our first release .
> Anyone who volunteer to take ?
> Here is the task list, you can reply with it with your interested task,
> Thanks
>
>
> Here is the task list：
> 1. Get all dependency third party’s copyright and
> apppend them to brpc License file
>
> 2. Add Notice and Disclaimer file to mention its copyright
> belong to apache foundation
>
> 3. Make a short license header, and add the header to all
> source files, including .h, .cpp, .java, etc
>
> 4. Check the source tarball to make sure it does not contain
> binary files except for data
>
> 5. Prepare release note to list all import checkin and features
>
> 6. Update Readme to add one section as “How to build”
>
>
> BTW：Here is one important things about include third party code:
> From its website https://apache.org/legal/resolved.html
> CATEGORY X: WHAT CAN WE NOT INCLUDE IN AN ASF PROJECT?¶
> Apache project forbid some third party software in it, it includes:
> 1. AGPL， LGPL，GPL
> 2. BSD + Fackbook patient
> 3.BSD-4-clouse
>
>
>
>
> 在 2019/3/19 下午3:04，“tan zhongyi”<je...@apache.org> 写入:
>
> Here is one example from Doris's RD
> Doris just released its first apache version,
> The owner write a document step by step, very details
>
> Here it is :
> http://doris.apache.org/policy/release_process.html
>
>
>
>
>
> 在 2019/3/18 下午11:26，“tan zhongyi”<zh...@gmail.com> 写入:
>
> Hi， guys,
>
> We need to release our first apache release for brpc in Q2.
>
> And it will be a great step to be an TOP level apache project for
> brpc.
>
> Here is some tasks that need to be done for the release after I
> refer to document from apache.org
>
>
> 1. Get all dependency third party’s copyright and apppend them
> to brpc License file
>
> 2. Add Notice and Disclaimer file to mention its copyright
> belong to apache foundation
>
> 3. Make a short license header, and add the header to all
> source files, including .h, .cpp, .java, etc
>
> 4. Check the source tarball to make sure it does not contain
> binary files except for data
>
> 5. Prepare release note to list all import checkin and features
>
> 6. Update Readme to add one section as “How to build”
>
>
>
>
> When we finish these tasks, then we need to open a thread to vote
> on dev@brpc.apache.org<ma...@brpc.apache.org>,
> If got approved, we need to open another vote on incubator mail
> list.
> If not approved, we should make changes according to our mentor
> or other’s suggestion, and vote again.
>
> I remember that it is very common to have several vote for the
> first release.
>
> That’s all for a release, anyone have comments?
> Thanks
>
>
>
>
Re: the tasklist that needed for the first apache release
Posted by tan zhongyi <zh...@gmail.com>.
Hi， all，
We need to assign task for our first release .
Anyone who volunteer to take ?
Here is the task list, you can reply with it with your interested task,
Thanks
Here is the task list：
1. Get all dependency third party’s copyright and apppend them to brpc License file
2. Add Notice and Disclaimer file to mention its copyright belong to apache foundation
3. Make a short license header, and add the header to all source files, including .h, .cpp, .java, etc
4. Check the source tarball to make sure it does not contain binary files except for data
5. Prepare release note to list all import checkin and features
6. Update Readme to add one section as “How to build”
BTW：Here is one important things about include third party code:
From its website https://apache.org/legal/resolved.html
CATEGORY X: WHAT CAN WE NOT INCLUDE IN AN ASF PROJECT?¶
Apache project forbid some third party software in it, it includes:
1. AGPL， LGPL，GPL
2. BSD + Fackbook patient
3.BSD-4-clouse
在 2019/3/19 下午3:04，“tan zhongyi”<je...@apache.org> 写入:
Here is one example from Doris's RD
Doris just released its first apache version,
The owner write a document step by step, very details
Here it is :
http://doris.apache.org/policy/release_process.html
在 2019/3/18 下午11:26，“tan zhongyi”<zh...@gmail.com> 写入:
Hi， guys,
We need to release our first apache release for brpc in Q2.
And it will be a great step to be an TOP level apache project for brpc.
Here is some tasks that need to be done for the release after I refer to document from apache.org
1. Get all dependency third party’s copyright and apppend them to brpc License file
2. Add Notice and Disclaimer file to mention its copyright belong to apache foundation
3. Make a short license header, and add the header to all source files, including .h, .cpp, .java, etc
4. Check the source tarball to make sure it does not contain binary files except for data
5. Prepare release note to list all import checkin and features
6. Update Readme to add one section as “How to build”
When we finish these tasks, then we need to open a thread to vote on dev@brpc.apache.org<ma...@brpc.apache.org>,
If got approved, we need to open another vote on incubator mail list.
If not approved, we should make changes according to our mentor or other’s suggestion, and vote again.
I remember that it is very common to have several vote for the first release.
That’s all for a release, anyone have comments?
Thanks
Re: the tasklist that needed for the first apache release
Posted by tan zhongyi <zh...@gmail.com>.
Here is one example from Doris's RD
Doris just released its first apache version,
The owner write a document step by step, very details
Here it is :
http://doris.apache.org/policy/release_process.html
在 2019/3/18 下午11:26，“tan zhongyi”<zh...@gmail.com> 写入:
Hi， guys,
We need to release our first apache release for brpc in Q2.
And it will be a great step to be an TOP level apache project for brpc.
Here is some tasks that need to be done for the release after I refer to document from apache.org
1. Get all dependency third party’s copyright and apppend them to brpc License file
2. Add Notice and Disclaimer file to mention its copyright belong to apache foundation
3. Make a short license header, and add the header to all source files, including .h, .cpp, .java, etc
4. Check the source tarball to make sure it does not contain binary files except for data
5. Prepare release note to list all import checkin and features
6. Update Readme to add one section as “How to build”
When we finish these tasks, then we need to open a thread to vote on dev@brpc.apache.org<ma...@brpc.apache.org>,
If got approved, we need to open another vote on incubator mail list.
If not approved, we should make changes according to our mentor or other’s suggestion, and vote again.
I remember that it is very common to have several vote for the first release.
That’s all for a release, anyone have comments?
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@brpc.apache.org
For additional commands, e-mail: dev-help@brpc.apache.org