[
https://issues.apache.org/jira/browse/SAMZA-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14082651#comment-14082651
]
Chris Riccomini commented on SAMZA-363:
---------------------------------------
bq. will we use "unstable" for the branch name?
Yes, that's what I was thinking. Do you (or anyone else) have another
preference? Unstable seemed good since it's suitably scary to keep normal devs
from trying to mess with it. This seemed ideal since it could be broken as we
evolve Samza's master branch.
bq. 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...
This is the trade-off with your approach. I agree it makes more sense. My fear
was that people would run git clone on the repo without a branch name, and
would get the unstable branch by default. [~jghoman], I think you had some
preference against this as well, right?
bq. So I am not very consistent in this thought.
Me neither. I don't feel really strongly one way or the other. The scheme I've
proposed is more confusing for us. The scheme you've proposed is more confusing
for Samza users. Neither one is so distasteful or bad that it can't be made to
work.
> 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)
