Hey Martin,

Great, I've made your changes. I've also updated the download page with
instructions on how to get the source release as well as the Maven
binaries.

I've submitted the revised blog post for review. Apparently jfarrell has
to approve it. The permalink will be:

  https://blogs.apache.org/samza/entry/announcing_the_release_of_apache

Cheers,
Chris

On 7/7/14 3:03 AM, "Martin Kleppmann" <[email protected]> wrote:

>Hi Chris,
>
>Nice post! I was wondering if it would be worth adding a bit of context
>at the start, for people who don't yet know about Samza: briefly mention
>what Samza is, what problem it solves, that it originated and is used in
>production at LinkedIn, that it has already attracted a diverse group of
>contributors from outside LinkedIn.
>
>The bullet point lists are probably at a lower level of detail than most
>readers would care about, but they give the overall impression of a
>healthy project, so I think they're good to include.
>
>If the links (all the JIRA references) get stripped out, it would be a
>much less valuable post. If the Apache blog won't let us post links,
>should we post it somewhere else?
>
>Re binary release: we probably won't have a binary release (SAMZA-311)
>for 0.7.0, only the Maven artifacts (SAMZA-199). But when the Maven
>artifacts are up, we could add instructions to
>http://samza.incubator.apache.org/startup/download/ with a pom.xml
>example, and also update hello-samza to use the 0.7.0 release.
>
>Typo: "SAMZA-SAMZA-253"
>
>Best,
>Martin
>
>On 7 Jul 2014, at 00:34, Chris Riccomini
><[email protected]> wrote:
>
>> Hey Guys,
>> 
>> I'm working on a blog post for the Apache Samza 0.7.0 release. The
>>draft is available here:
>> 
>>  https://gist.github.com/criccomini/be96696f819b4d60c1b2
>> 
>> I'm planning to post it here:
>> 
>>  https://blogs.apache.org/samza
>> 
>> The plain-text (URLs stripped by Apache, most likely):
>> 
>> 
>> Announcing the release of Apache Incubator Samza 0.7.0
>> 
>> 
>> I am very excited to announce that Apache Incubator Samza 0.7.0 has
>>been released. In all, 156 JIRAs were
>>resolved<https://issues.apache.org/jira/browse/SAMZA-309?jql=project%20%3
>>D%20SAMZA%20AND%20fixVersion%20%3D%200.7.0%20AND%20status%20in%20(Resolve
>>d%2C%20Closed)> in this release. Notable work done includes:
>> 
>>  *   Initial import of code into Apache.
>>(SAMZA-1<https://issues.apache.org/jira/browse/SAMZA-1>)
>>  *   Upgraded to YARN 2.2 from YARN 2.05-alpha.
>>(SAMZA-9<https://issues.apache.org/jira/browse/SAMZA-9>)
>>  *   
>>Numerous<https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA
>>%20AND%20fixVersion%20%3D%200.7.0%20AND%20status%20in%20(Resolved%2C%20Cl
>>osed)%20and%20component%20%3D%20kv> state management bug fixes.
>>  *   Java 7 support.
>>(SAMZA-16<https://issues.apache.org/jira/browse/SAMZA-16>)
>>  *   A 
>>ton<https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AN
>>D%20fixVersion%20%3D%200.7.0%20AND%20status%20in%20(Resolved%2C%20Closed)
>>%20and%20component%20%3D%20docs> of work on
>>documentation<http://samza.incubator.apache.org/learn/documentation/0.7.0
>>/>, tutorials<http://samza.incubator.apache.org/learn/tutorials/0.7.0/>,
>>hello-samza<http://samza.incubator.apache.org/startup/hello-samza/0.7.0/>
>>, and 
>>Javadocs<http://samza.incubator.apache.org/learn/documentation/0.7.0/api/
>>javadocs/>.
>>  *   Scala 2.10 support, and removal of support for Scala 2.8
>>(SAMZA-128<https://issues.apache.org/jira/browse/SAMZA-128>,
>>SAMZA-160<https://issues.apache.org/jira/browse/SAMZA-160>)
>>  *   One-off resets for input stream offsets.
>>(SAMZA-180<https://issues.apache.org/jira/browse/SAMZA-180>)
>>  *   Upgrade to support Apache Kafka<http://kafka.apache.org/> 0.8.1,
>>which includes log compaction.
>>(SAMZA-180<https://issues.apache.org/jira/browse/SAMZA-180>)
>>  *   A consensus based shutdown API.
>>(SAMZA-SAMZA-253<https://issues.apache.org/jira/browse/SAMZA-SAMZA-253>)
>> 
>> Source (TODO link) and binary (TODO link) downloads of the release are
>>available here (TODO link).
>> 
>> 
>> We've also made a lot of community progress during this release:
>> 
>>  *   Added 4 new
>>committers<http://samza.incubator.apache.org/community/committers.html>
>>(Garry Turkington, Martin Kleppmann, Zhijie Shen, and Yan Fang).
>>  *   Accepted patches from 14 distinct contributors
>>  *   Presented on Samza's architecture and
>>usage.<http://wiki.apache.org/samza/PapersAndTalks>
>>  *   Had over 1000 emails to the developer mailing
>>list<http://mail-archives.apache.org/mod_mbox/incubator-samza-dev/>.
>> 
>> Even after all this work, there's still a lot to be
>>done<https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20A
>>ND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC>. In
>>our next release (0.8.0), we're planning to focus on performance. This
>>work includes:
>> 
>>  *   Switching Samza's state feature to use RocksDB instead of LevelDB.
>>(SAMZA-236<https://issues.apache.org/jira/browse/SAMZA-236>)
>>  *   Supporting pluggable partition-container assignment strategies.
>>(SAMZA-71<https://issues.apache.org/jira/browse/SAMZA-71>)
>>  *   Improving consumer performance.
>>(SAMZA-245<https://issues.apache.org/jira/browse/SAMZA-245>)
>>  *   Upgrading Samza's YARN UI.
>>(SAMZA-32<https://issues.apache.org/jira/browse/SAMZA-32>,
>>SAMZA-237<https://issues.apache.org/jira/browse/SAMZA-237>,
>>SAMZA-290<https://issues.apache.org/jira/browse/SAMZA-290>)
>> 
>> Now is a great time to get involved. You can start by running through
>>the 
>>hello-samza<http://samza.incubator.apache.org/startup/hello-samza/0.7.0/>
>> tutorial, signing up for the mailing
>>list<http://samza.incubator.apache.org/community/mailing-lists.html>,
>>and grabbing some newbie
>>JIRAs<https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20
>>AND%20labels%20%3D%20newbie%20AND%20status%20%3D%20Open>.
>> 
>> 
>> I'd like to close by thanking everyone who's been involved in the
>>project. It's been a great experience to be involved in this community,
>>and I look forward to its continued growth.
>> 
>> Feedback welcome. :)
>> 
>> Cheers,
>> Chris
>

Reply via email to