[GitHub] [openwhisk-wskdebug] alexkli commented on a change in pull request #50: add "Releasing" section to readme

[GitBox <gi...@apache.org>]

alexkli commented on a change in pull request #50: add "Releasing" section to readme
URL: https://github.com/apache/openwhisk-wskdebug/pull/50#discussion_r408449769
 
 

 ##########
 File path: README.md
 ##########
 @@ -689,6 +690,16 @@ See also [invoker.js](src/invoker.js). Note that some of these might not be set
 
 Contributions are welcomed! Read the [Contributing Guide](.github/CONTRIBUTING.md) for more information.
 
+<a name="releasing"></a>
+## Releasing
+
+Releases are done using the [Apache OpenWhisk Release Process](https://github.com/apache/openwhisk-release/blob/master/docs/release_instructions.md).
+
+`wskdebug` releases are available:
+- on the [Apache OpenWhisk download page](https://openwhisk.apache.org/downloads), stored on Apache mirrors (canonical release)
+- on NPM as [@openwhisk/wskdebug](https://www.npmjs.com/package/@openwhisk/wskdebug) (convenience)
+- as [Github Releases](https://github.com/apache/openwhisk-wskdebug/releases) (linked to source history)
 
 Review comment:
   Note this section is geared towards the release manager, not users. This comes at the very end, and install instructions at the top only mention npm.
   
   BTW, how would an attacker tamper with github releases? If they can do that, they can also mess with the sources that are used to create all the releases.
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services