Hey Guys, Code is up. JIRA is closed. Hello-samza is up.
Please go and try out hello-samza, and make sure it works for you (it does for me). I'll open a second ticket for the project refactor. Cheers, Chris On 8/11/13 4:51 PM, "Chris Riccomini" <[email protected]> wrote: >Hey Jay, > >Updated JIRA with proposed sequence: > > https://issues.apache.org/jira/browse/SAMZA-1 > >I think you're in the minority with respect to samza.*... but maybe I'm >wrong? Sriram, Jakob? > >Also, I rolled a few other changes (package refactor, and project >refactor) in with this change. It's aggressive, but better now than >later. The package refactor is the only one that should really be >breaking (aside from build files), and that refactor has to be done >either way. Thoughts? > >Cheers, >Chris >________________________________________ >From: Jay Kreps [[email protected]] >Sent: Sunday, August 11, 2013 4:41 PM >To: [email protected] >Cc: [email protected] >Subject: Re: CCLA filed -- code drop imminent > >Sweet. Apache doesn't require any particular package iirc. Personally I >prefer the shorter samza.* because I always thought using the website URL >was silly and it looks cleaner (also matches Kafka). Some people don't >like this, though. > >-jay > >Sent from my iPhone > >On Aug 11, 2013, at 4:30 PM, Chris Riccomini <[email protected]> >wrote: > >> Hey Guys, >> >> When doing the import, should I change the package space to be: >> >> samza.* >> >> Or >> >> org.apache.samza.* >> >> I'm inclined to do org.apache.samza.* >> >> Cheers, >> Chris >> ________________________________________ >> From: Chris Riccomini [[email protected]] >> Sent: Sunday, August 11, 2013 9:18 AM >> To: [email protected] >> Subject: CCLA filed -- code drop imminent >> >> Hey Guys, >> >> Our CCLA for Samza just went through. I'll try and get the code drop >>going later today, or tomorrow, as time permits (sick baby). >> >> Cheers, >> Chris
