Great news! Once the community is satisfied with the state of the artifact, we'll need to go over any packaged dependencies to make sure the licensing is in order. The following is a good resource:
http://www.apache.org/legal/resolved.html However, scanning the Oozie source, I didn't find any binary artifacts, save: ./core/src/test/resources/wordcount-simple_Linux-amd64-64_h20: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.4.0, not stripped ./core/src/test/resources/wordcount-simple_Linux-i386-32_h20: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, not stripped ./core/src/test/resources/wordcount-simple_Mac_OS_X-x86_64-64_h20: Mach-O executable i386 Other than these, it looks like the licensing/redistribution will be dead simple as long as it's a source release. Where do these come from? We'll also want to run RAT over the release tarball: http://incubator.apache.org/rat This should be enough to get started: http://apache.org/dev/release.html#what-must-every-release-contain -C On Tue, Jan 24, 2012 at 6:04 PM, Mohammad Islam <[email protected]> wrote: > Hi, > I would like to start the process of releasing Oozie 3.1 (QE-certified and > currently used at Yahoo production). > > 3.1 branch is already created. > > Please don't commit anything until further email. > > I will let know during the first release process. > > Since this will be our first release at Apache, we expect to learn a lot of > new thing. Please bear with us. > > Regards, > Mohammad
