rabbah commented on a change in pull request #304: updated post-vote release 
instructions
URL: https://github.com/apache/openwhisk-release/pull/304#discussion_r327253167
 
 

 ##########
 File path: docs/release_instructions.md
 ##########
 @@ -162,22 +162,89 @@ restart the process with new candidate releases.  Update 
your
 `config.json` file by incrementing the `rc` number and changing git
 hashes.
 
-### Publishing a Successful Release
-
-TODO: This portion of the documentation and scripting still needs to be 
updated.
-
-  10. [Publish the release artifacts to Apache release 
directory](publish_apache_directory.md)
-      You should receive an email from reporter.apache.org asking you to add 
your version data
-      to its database shortly after you commit to the dist svn.  Please follow 
the link and
-      add the information (this is useful for generating board reports).
-  11. [Tag the commit IDs in the Github repository for the 
project](tag_release.md)
-  12. [Generate the release notes](generate_release_notes.md)
-  13. If appropriate, update dockerhub `latest` tags.
-  14. If appropriate update deploy-kube and docker-compose tag info to pick up 
new images.
-  15. Submit a PR to update the downloads page.
-
-  20. Announce the release -- must wait until website PR is merged and Jenkins 
publishes site.
-  30. Cleanup the artifacts from the release process:
-      a. Remove the rc files from staging.
-      b. Remove the previous If there is a previous released version, remove 
it from Apache release directory
-         (it will automatically still be available via the Apache archive 
server).
+### Publishing a Successful Release to Apache Dist Servers
+
+After a successful vote, the release manager will commit the artifacts
+being released to the openwhisk subdir of the Apache dist svn.
 
 Review comment:
   openwhisk
   ```suggestion
   being released to the OpenWhisk subdir of the Apache dist svn.
   ```

----------------------------------------------------------------
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:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to