You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Yan Fang (JIRA)" <ji...@apache.org> on 2014/08/01 20:05:39 UTC

[jira] [Commented] (SAMZA-363) Create a development branch for hello-samza

    [ https://issues.apache.org/jira/browse/SAMZA-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14082632#comment-14082632 ] 

Yan Fang commented on SAMZA-363:
--------------------------------

{quote}
unstable: uses Samza's master branch.
{quote}
will we use "unstable" for the branch name?

I agree on this proposal and would like to have branches for different versions. That makes sure users can run hello-samza against different versions.

Only one thought: can we use hello-samza master maps to Samza's mater branch? It seems more intuitive... the latest release version always will have a version number, (current 0.7.0, later 0.8.0), we can just use this as the branch name. I know, that will actually make the master branch of hello samza unrunable...So I am not very consistent in this thought. 

> 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)