> If we already trust a contributor to release, I would say, he/she is qualified to be a committer. The release is a more serious thing than general contributing.
I just look around the codes contribution from apisix-website & apisix-dashboard repos[1][2], yes, there have many Web FIX contributions from Baoyuan since Aug 2020. Back to Baoyuan's question, I personally believe he could help to gather the CHANGELOG for the coming Apache APISIX Dashboard 2.10's Release, but because it's more official and serious, we'd better keep the process going as related policy.[3] Sheng Wu, thanks for your clarification, I will seek help from our committers to release the new version, and will think about Baoyuan's contribution :) [1] https://github.com/apache/apisix-website/commits?author=baoyuantop [2] https://github.com/apache/apisix-dashboard/commits?author=baoyuantop [3] https://apisix.apache.org/docs/general/release-guide Best Regards! @ Zhiyuan Ju <https://github.com/juzhiyuan> Sheng Wu <wu.sheng.841...@gmail.com> 于2021年12月10日周五 10:34写道： > I think you should be a committer to run release process, and PMC needs to > approve it(or ask for another round). > There are several things > 1. Release is official, it should be signed(gpg) by Apache account. > 2. Release manager should know what to check and what is the release > policy. > 3. Release manager should get familiar with when a release should be cut. > > If we already trust a contributor to release, I would say, he/she is > qualified to be a committer. Release is a more serious thing than general > contributing. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > Baoyuan <baoyuan....@gmail.com> 于2021年12月10日周五 10:09写道： > > > Hi Community, I have an idea about volunteers to help the community with > a > > release. > > > > It is well known that each release step is fixed and repetitive and it > may > > take some of the individual's time, so I was wondering if we could find > > volunteers in the community to assist with the release. > > > > One problem here is that some steps in the release may not be completed > by > > non-committer members, I think the committer can make some assistance and > > then leave the ones that are not related to permissions to volunteers > > (sending emails, submitting PRs). > > > > I'd be happy to help with this if I can, what do you think? > > >
