ok, I'll take task 5 On Fri, Mar 29, 2019 at 4:07 PM tan zhongyi <zhongyi....@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”<huwen...@baidu.com> 写入: > > I would like take 6. > > > > 在 2019/3/28 09:23，“tan zhongyi”<zhongyi....@gmail.com> 写入: > > Thanks，zhangyi， > > Anyone else who want to volunteer to take some task？ > > 在 2019/3/27 下午10:17，“Zhangyi Chen”<frozen....@gmail.com> 写入: > > I would like take 1 and 2. > > On Tue, Mar 26, 2019 at 2:25 PM tan zhongyi < > zhongyi....@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”<jerry...@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....@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<mailto:dev@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 >
