Hi there, I am picking up some questions Johannes asked regarding npm releases and the ASF/ASF releases and reposting them, it seems they got lost in [1].
> And how do we handle npm releases? Currently Nuno Job, Pedro Teixeira > and me have write access on npmjs.com. This needs to be changed so we > maybe can have a CouchDB account? Also, how does the Apache release > procedure work for npm packages? That is a really good question and also applies to nmo. Btw: How often do you release new nano versions? If I remember right an official ASF release must be a tarball on ASF servers. npm creates tarballs before it publishes it and I think it can also create just a tarball at an output location [1] While an official release must be located on an ASF server as an tarball and there must be a vote on them, you can additionally host the release additionally somewhere else (e.g. npm) Jan told me Hoodie will use the special npm tag next for their latest releases. The latest official ASF release from nano could then be nano@latest/nano@major.minor.patch and the latest of the git master could be nano@next. Every few weeks we then vote and release a new official ASF release. Apache Cordova is also releasing their npm packages on a weekly basis, most of the process is automated through a cli client [2]. They probably use an npm account registered for private@ to publish new packages (same concept we use for our twitter account) I would be interested in helping to automate our releases, probably together with Bastian who is doing great work for the new CI. Do you have other suggestions how to handle it? Best, Robert [1] http://mail-archives.apache.org/mod_mbox/couchdb-dev/201507.mbox/%3C55A6868D.9050809%40netzmerk.com%3E [2] https://github.com/apache/cordova-coho/blob/master/docs/plugins-release-process.md
