You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2020/03/11 17:25:14 UTC
[GitHub] [openwhisk-release] dgrove-oss opened a new pull request #332:
document wskdebug 1.2.0
dgrove-oss opened a new pull request #332: document wskdebug 1.2.0
URL: https://github.com/apache/openwhisk-release/pull/332
----------------------------------------------------------------
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
[GitHub] [openwhisk-release] dgrove-oss commented on a change in pull
request #332: document wskdebug 1.2.0
Posted by GitBox <gi...@apache.org>.
dgrove-oss commented on a change in pull request #332: document wskdebug 1.2.0
URL: https://github.com/apache/openwhisk-release/pull/332#discussion_r393158202
##########
File path: docs/release_instructions.md
##########
@@ -290,11 +290,11 @@ into other runtime projects to build their images.
### Publishing to npm
-The openwhisk-client-js and openwhisk-composer project release npm
-packages built from each source release. The Release Manager should
-build and publish these packages manually using the openwhisk-bot
-credentials found in the npmjs.txt file in the accounts subdir of the
-PMC private svn.
+The openwhisk-client-js, openwhisk-composer, and openwhisk-wskdebug
+project release npm packages built from each source release. The
+Release Manager should build and publish these packages manually using
+the openwhisk-bot credentials found in the npmjs.txt file in the
+accounts subdir of the PMC private svn.
Review comment:
I'd be inclined to leave it out. Hopefully PMC members know where to find this (and will ask on @private if they don't).
----------------------------------------------------------------
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
[GitHub] [openwhisk-release] rabbah merged pull request #332: document
wskdebug 1.2.0
Posted by GitBox <gi...@apache.org>.
rabbah merged pull request #332: document wskdebug 1.2.0
URL: https://github.com/apache/openwhisk-release/pull/332
----------------------------------------------------------------
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
[GitHub] [openwhisk-release] rabbah commented on a change in pull request
#332: document wskdebug 1.2.0
Posted by GitBox <gi...@apache.org>.
rabbah commented on a change in pull request #332: document wskdebug 1.2.0
URL: https://github.com/apache/openwhisk-release/pull/332#discussion_r393125545
##########
File path: docs/release_instructions.md
##########
@@ -290,11 +290,11 @@ into other runtime projects to build their images.
### Publishing to npm
-The openwhisk-client-js and openwhisk-composer project release npm
-packages built from each source release. The Release Manager should
-build and publish these packages manually using the openwhisk-bot
-credentials found in the npmjs.txt file in the accounts subdir of the
-PMC private svn.
+The openwhisk-client-js, openwhisk-composer, and openwhisk-wskdebug
+project release npm packages built from each source release. The
+Release Manager should build and publish these packages manually using
+the openwhisk-bot credentials found in the npmjs.txt file in the
+accounts subdir of the PMC private svn.
Review comment:
should we provide a link to it here for convenience or leave it out for _security_?
----------------------------------------------------------------
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