For snapshot versions, I believe build tools are allowed to publish to the snapshot repo as needed. jenkins builds already support this and I am guessing travis should have similar provisions.
For releases ( with a disclaimer as binary artifacts are not considered part of an official release), the binary convenience artifacts would be publish via dist.apache.org. The general approach is to publish an RC to dist.apache/dev , get it voted upon by the community/PPMC ( followed by an IPMC vote on general@incubator ) and then move to /release after the vote is successful. As part of the RC creation, the release manager would do an appropriate mvn deploy ( this will go into a staging repo ) and also push the bits to dist.apache.org - both of which need to be signed. Will need to check more on travis and whether a tool can publish bits as all releases are meant to be signed by someone from the PPMC and using a tool would imply providing your secret keys to the tool. — Hitesh On Apr 5, 2016, at 7:23 AM, Gino Bustelo <g...@bustelos.com> wrote: > We are getting close to completing work to our build scripts (PR #13 > <https://github.com/apache/incubator-toree/pull/13>) to make the project > follow the Apache release criteria that we've been able to find through > search. Mainly auditing license headers, POM content, jar generation with > NOTICE/LICENSE files, etc. > > At this point we need someone with experience that can verify all the steps > we've done. Also, it is not clear to me what the process is to getting all > the assets published for a release vote. Several question are: > > 1. Can publishing of assets be automated using Travis? Including maven > publish, and binary package distribution. > 2. Where do we publish binary packages? Not talking about JARs, rather a > package with libraries and scripts to start/run Toree. > > Any help is appreciated... > > Thanks, > Gino
