You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polygene.apache.org by "Paul Merlin (JIRA)" <ji...@apache.org> on 2017/05/15 11:54:04 UTC
[jira] [Resolved] (POLYGENE-245) Process for Publish to NPM
registry
[ https://issues.apache.org/jira/browse/POLYGENE-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Merlin resolved POLYGENE-245.
----------------------------------
Resolution: Fixed
Process is now documented in `howto-releasing-apache.txt`
> Process for Publish to NPM registry
> -----------------------------------
>
> Key: POLYGENE-245
> URL: https://issues.apache.org/jira/browse/POLYGENE-245
> Project: Polygene
> Issue Type: New Feature
> Reporter: Niclas Hedhman
> Assignee: Paul Merlin
> Fix For: 3.0
>
>
> In http://www.apache.org/legal/release-policy#publication, there are some important bits that will affect our Yeoman project creator, especially that whatever is published there, needs to be published as source artifact first.
> So,
> 1. The tools/generator-polygene needs to be part of the source release.
> 2. The tools/generator-polygene should be part of the binary release for install on the user's system.
> 3. The tools/generator-polygene npm package is treated the same way as Maven published to Maven Central.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)