I found this article <http://incubator.apache.org/incubation/Incubation_Policy.html#Releases> explaining podling releases. It appears we should our own directory, under http://www.apache.org/dist/incubator/, to distribute our releases. This <http://www.apache.org/dev/release-publishing.html> seems to be the complete release process for binary package for apache projects. I found all of these links (and more) on the dev package under the releases section <http://www.apache.org/dev/#releases>.
On Tue, Apr 5, 2016 at 9:24 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 >
