[
https://issues.apache.org/jira/browse/SAMZA-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Riccomini resolved SAMZA-363.
-----------------------------------
Resolution: Fixed
Pushed latest branch:
https://git-wip-us.apache.org/repos/asf?p=incubator-samza-hello-samza.git;a=log;h=refs/heads/latest
# Added `install samza` command back to auto-build from samza's master branch.
# Upgraded YARN to 2.4.0.
# Upgraded Kafka to 2.10.
# pom.xml is now using 0.8.0-SNAPSHOT for samza's version number.
# pom.xml is now using 0.8.0 for project's version number.
There didn't seem to be any API incompatibilities. Ran the first job and it
worked.
> Create a development branch for hello-samza
> -------------------------------------------
>
> Key: SAMZA-363
> URL: https://issues.apache.org/jira/browse/SAMZA-363
> Project: Samza
> Issue Type: Bug
> Components: hello-samza
> Affects Versions: 0.8.0
> Reporter: Chris Riccomini
> Fix For: 0.8.0
>
>
> The hello-samza example project has only a single master branch right now.
> This branch is set to use the latest release of Samza (0.7.0, currently).
> We've been discussing creating a development branch for hello-samza so that
> developers can experiment with the unreleased version of Samza (0.8.0,
> currently the master branch for the samza repo).
> I'm proposing having the following branch structure:
> * master: uses the latest released version of Samza (currently 0.7.0).
> * unstable: uses Samza's master branch.
> * 0.X.0: all older (non-latest) releases will have their own branch.
> When we release 0.8.0, we will cut an 0.7.0 branch, and master will be
> switched to use 0.8.0. The unstable branch will always remain on samza's
> master branch.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
