houshengbo commented on issue #11: Create the project structure to release based on versions URL: https://github.com/apache/incubator-openwhisk-release/issues/11#issuecomment-359959426 The incubator-openwhisk-release itself is not part of the openwhisk projects to be released. It is a tool to manage the release of all the openwhisk projects. My intention is to make it a one-stop entry to access all the openwhisk projects. It does not have any significance here to use VCS tags for incubator-openwhisk-release. Maybe it is good idea to manage a single project in openwhisk series, like openwhisk, cli, wskdeploy, any runtime project. I hope the development of incubator-openwhisk-release could be as easy as possible for the users(in fact, release manager of openwhisk). We fork it under our name, create a PR, and request to merge into master. Each PR needs to turn on a Travis build, which only builds based on the files inside release/current, and only needs to verify the code, deploy the code, test the code if necessary. There is no need to package and push the source code upstream to apache directory. We only care about this folder, when we are developing, before any release milestone we decide. As we feel confident in all the hash values saved in release/current/config.json, and decide to propose it as buldled openwhisk projects to release, we can copy them into the folder with name the same to the release name, e.g. 1.0.0 milestone-1. This change can be proposed in a PR as well. After we receive the consent from the community to release 1.0.0 milstone-1, we merge the above PR, and tag the commit 1.0.0, so it kick off travis build. Travis sees the tag name, and decide to build based on the config.json under releases/1.0.0/milestone-1(2 or 3)/. In the end, packages of the source code with license, notice, changelog, installation files, etc, will be pushed into the online designated directory of Apache.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
