Hi Bertrand, The responsibility of the repository incubator-openwhisk-release is to make sure openwhisk will be released based on Apache release process for projects, and compliant with Apache requirements. The implementation follows all the necessary steps in order to release the project, including but not limited to, packaging the source code with valid notice and license, signing the artifacts with PGP key, uploading them into the apache directory for vote, etc. This is a tool facilitating the release manager from having source code only to having all the artifacts ready online for vote. When we pass the vote, the artifacts can be moved to the release folder of apache. If not, we can retrospect to any earlier step to prepare another set of artifacts proposed to release.
So far, as Carlos said, we are almost ready o release the source code, except that we need to verify in each repository that there are correct license headers for source code files. Best wishes. Vincent Hou (侯胜博) Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: [email protected], Phone: +1(919)254-7182 Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States From: Carlos Santana <[email protected]> To: [email protected] Date: 03/27/2018 12:42 PM Subject: Re: Updates of OpenWhisk Release Good progress Vincent I reviewed the tutorial with steps for doing the release and opened an issue [1] to update the document that there needs to be a second vote on incubator list, which is the one that would provide the final set of votes to release. Bertrand. >Are those tools ready for the PPMC to start preparing the first release of a significant OpenWhisk module? I think we almost ready, Only thing I think there are a set of source files that are missing the Apache License header. Other than this I think we should be ready to cut the first RC and start vote on dev list. [1] https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_incubator-2Dopenwhisk-2Drelease_issues_72&d=DwIBaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=LUNmCHjmrhrkjp9ZF9fhwg&m=QxcCo-Ge42RjHK-kC6S18kf8r0DQKA0Mw5HDwpg7XK8&s=mIp_-xVzi9uELfc9ydoytMZPw39VHT4olqwSvgk9nuY&e= -- Carlos On Tue, Mar 27, 2018 at 7:16 AM Bertrand Delacretaz <[email protected]> wrote: > Hi, > > On Mon, Mar 26, 2018 at 4:40 PM, Vincent S Hou <[email protected]> wrote: > > ...Our tool to manage the release process of OpenWhisk is currently on > track > > and open to any tests and comments.... > > As an incubation mentor I'm not necessarily interested in all the > details of the release tools, but more on the overall release process > and artifacts. > > Are those tools ready for the PPMC to start preparing the first > release of a significant OpenWhisk module? > > If yes I think that's the best way of validating them and the > understanding of the release process by the PPMC. > > The way it works is that a release candidate is voted upon here before > moving to the Incubator PMC vote which is required to authorize the > release. > > So having imperfect release candidates is not a problem, they can be > discussed and improved here without bothering the Incubator PMC. > > -Bertrand >
