We can actually start publishing the jars to maven immediately; I'm hoping to work on this throughout the week in addition to the actual release preparation. The maven jars in a repo will be useful for those developing Samza apps.
The actual release itself will be of a specific source control revision, bundled as a tgz for inspection. The separate, compiled binary release is done as a convenience to the users. Often projects just do source releases in order to avoid the rigmarole of getting all the transitive dependencies sorted out in the notice and license files. I'd recommend we do this immediately though, to make it as easy as possible for users to get started with a release of Samza. -Jakob On Sat, May 31, 2014 at 9:06 AM, Martin Kleppmann <[email protected]> wrote: > When we do the 0.7.0 Apache release, we are planning to release artifacts > to Maven (https://issues.apache.org/jira/browse/SAMZA-199), which is > great. However, I don't remember discussion of a standalone binary release. > Is that also planned? > > I am thinking of the following: a .zip/.tar.gz file which includes all > dependencies, and which has the user-facing shell scripts (run-job.sh, > kill-yarn-job.sh, checkpoint-tool.sh) in a bin directory in the archive, > wired up and ready to go. Say you're a user who has a job config on your > machine, and a job package (already built) somewhere where YARN can reach > it. You should be able to download that Samza release, unpack it, and > immediately run `./samza-0.7.0/bin/run-job.sh > --config-path=file:///path/to/job.conf` to submit a job. > > I think the way it works in hello-samza (where you first have to build an > artifact of your own job, and then unpack it again to get the shell scripts > for submitting the job) will confuse new users. > > What do you think? Sorry if this is already planned, I just don't recall > seeing anything like this mentioned anywhere in JIRA/mailing list/build > config. > > Martin > >
