Sorry for the hold up Kam. You will want to look at http://www.apache.org/dev/release.html
We will need especially close attention to the contents of the LICENSE and NOTICE files when making the first release. That FAQ talks about them starting here http://www.apache.org/dev/release.html#license . If you are only releasing a source package it is pretty straightforward. The signed source package is mandatory anyway. If you want to also release binary convenience packages with bundled dependencies, the LICENSE and NOTICE files for the binary packages must enumerate all non-ASF licenses of the bundled dependencies. Over on HBase we ended up automating the generation of LICENSE and NOTICE files using quite a bit of Maven hackery. Perhaps you'll want to start with only making a source package. On Wed, Jun 8, 2016 at 3:12 PM, Kam Kasravi <[email protected]> wrote: > The release process I've been looking at is here - > http://www.apache.org/dev/release-publishing.html and the maven > publishing link within this document. > > On Wed, Jun 8, 2016 at 2:59 PM, Kam Kasravi <[email protected]> wrote: > >> Hi Andy >> >> I would like to begin staging for a candidate release and call for a vote. >> You had mentioned there were some notes/caveats on the release process >> you could provide? >> >> Thanks >> Kam >> > > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
