This mail is for all the developer, so anyone can jump in to improve the documents. So we normal encourage the people to take the task by them self.
I guess Asif and YanBo already have some experience about the release kit check list there. I can start some points here: Release kit 1. Check if the signed key is OK, the release candidate is signed rightly. 2. Running the binary with the instruction of the README. 3. Running some function test with the binary kit ( we need to check windows and linux version at the same time). For the Source code we need to make sure the we flowed the license instruction You can use the rat tool[1] to check the license header, and we need to make sure the third party dependency or files copyright are rightly mentioned in NOTICE file. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, May 24, 2018 at 2:17 PM, Zen Lin <[email protected]> wrote: > Yeah , thanks to Willem. > > I am sorry I just continuous focused on the community promotion, thus I > lacked of experience about the release. > Maybe in future, I will try to learn about that once I have time. > I think some guys that have contributed on the previous release can help > the community to do this, thus I created a JIRA issue [1] to track this. > > [1] https://issues.apache.org/jira/browse/SCB-608 > > Best Regards, > --- > Zen Lin > [email protected] > Focused on Micro Service and Apache ServiceComb > > 2018-05-24 8:40 GMT+08:00 Willem Jiang <[email protected]>: > > > We have a release guide[1] for the release processing. > > We can add a check list section for verifying the kit. Please feel free > to > > send a PR for it. > > > > [1]https://servicecomb.incubator.apache.org/developers/release-guide/ > > > > > > Willem Jiang > > > > Blog: http://willemjiang.blogspot.com (English) > > http://jnn.iteye.com (Chinese) > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Wed, May 23, 2018 at 7:56 PM, Zen Lin <[email protected]> > > wrote: > > > > > I suggest adding a action, black crow scanning. > > > And also , shall we comb out what should be check carefully first > > according > > > to the first release prepare, then put it to our website. > > > Thus we can just check it step by step accroding to the checklist when > we > > > release the next version. > > > > > > Hi Yangbo, > > > To the latest release, we have find some easily misunderstanding places > > in > > > the Apache rules, we can output a blog about that then put it to the > > Apache > > > blog, thus to help other Apache incubating projects. > > > > > > Best Regards, > > > --- > > > Zen Lin > > > [email protected] > > > Focused on Micro Service and Apache ServiceComb > > > > > > 2018-05-23 16:22 GMT+08:00 Willem Jiang <[email protected]>: > > > > > > > Hi team, > > > > > > > > As we are heading to a new release, let me share a tools from the > > > recently > > > > release check in the incubator generic mailing list. > > > > > > > > I point out some License issue[1] by checking the third party jars, > > > pulsar > > > > did a quick fix[2] with a new script. I highly recommend that we can > > > > leverage this script to avoid the same mistake. > > > > > > > > Any thought？ > > > > > > > > [1] > > > > https://lists.apache.org/thread.html/ac5d0ae4367c7d11153444adc6317e > > > > bdd4aa93f51adcba7d548f8097@%3Cgeneral.incubator.apache.org%3E > > > > > > > > [2]https://github.com/apache/incubator-pulsar/pull/1820 > > > > > > > > > > > > > > > > Willem Jiang > > > > > > > > Twitter: willemjiang > > > > Weibo: 姜宁willem > > > > > > > > > >
