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
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
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)
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
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
