couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andy Wenk <a...@nms.de>
Subject Re: npm releases and ASF releases
Date Thu, 23 Jul 2015 13:37:28 GMT
On 23 July 2015 at 13:45, Jan Lehnardt <jan@apache.org> wrote:

>
> > On 23 Jul 2015, at 13:40, Robert Kowalski <rok@kowalski.gd> wrote:
> >
> > 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)
>
> > Do you have other suggestions how to handle it?
>
> I think the suggested approach is fine. Unless you hear any objections
> in the next 72 hours, feel free to go ahead and implement it :)
>
>
> > I would be interested in helping to automate our releases, probably
> > together with Bastian who is doing great work for the new CI.
>
> I recommend using https://github.com/semantic-release/semantic-release
> for this.
>
> Best
> Jan
> --


Both points from Robert and Jan sound good to me. And yes +1 for semantic
releases.

Cheers

Andy



>
> >
> >
> > 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
>
> --
> Professional Support for Apache CouchDB:
> http://www.neighbourhood.ie/couchdb-support/
>
>


-- 
Andy Wenk
Hamburg - Germany
RockIt!

http://www.couchdb-buch.de
http://www.pg-praxisbuch.de

GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588

https://people.apache.org/keys/committer/andywenk.asc

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message