[jira] [Comment Edited] (ARROW-1577) [JS] Package release script for NPM modules

["Paul Taylor (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARROW-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178440#comment-16178440 ] 

Paul Taylor edited comment on ARROW-1577 at 9/25/17 1:54 AM:
-------------------------------------------------------------

[~wesmckinn] does the voting process determine whether the release is published to npm? or should I include the `npm publish` steps in the release script?


was (Author: paul.e.taylor):
[~wesmckinn] does the voting process determine whether the tarballs are published to npm? or should I include the `npm publish` steps in the release script?

> [JS] Package release script for NPM modules
> -------------------------------------------
>
>                 Key: ARROW-1577
>                 URL: https://issues.apache.org/jira/browse/ARROW-1577
>             Project: Apache Arrow
>          Issue Type: New Feature
>          Components: JavaScript
>    Affects Versions: 0.8.0
>            Reporter: Wes McKinney
>
> Since the NPM JavaScript module may wish to release more frequently than the main Arrow "monorepo", we should create a script to produce signed NPM artifacts to use for voting:
> * Update metadata for new version
> * Run unit tests
> * Create package tarballs with NPM
> * GPG sign and create md5 and sha512 checksum files
> * Upload to Apache dev SVN
> i.e. like https://github.com/apache/arrow/blob/master/dev/release/02-source.sh, but only for JavaScript.
> We will also want to write instructions for Arrow developers to verify the tarballs to streamline the release votes



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)