You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2014/08/01 23:07:39 UTC
[jira] [Assigned] (SAMZA-363) Create a development branch for
hello-samza
[ https://issues.apache.org/jira/browse/SAMZA-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Riccomini reassigned SAMZA-363:
-------------------------------------
Assignee: Chris Riccomini
> 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
> Assignee: 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)