curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ioannis Canellos <>
Subject Re: [DISCUSS] Git workflow
Date Sun, 21 Jul 2013 09:28:21 GMT
Agree. Releasing directly from master is so much easier.

Since we are already using semantic versions, we may also want to create a
branch each time we advance a minor version, so that we can backport bug
fixes that are applicable to previous minor versions (e.g. we could use a
curator-2.0.x if we ever going to need a curator-2.0.2-incubating for bug

On Sun, Jul 21, 2013 at 1:26 AM, Jordan Zimmerman <> wrote:

> Currently, we're using a Github-flow-like workflow: a branch for the
> current release; a master branch; branches for each Jira.
> I've come to think that the current release branch is unnecessary and
> confusing. For example, I keep forgetting if I've merged all needed Jira
> branches into it. What do folks think about just using master for the
> current release branch?
> Also, feel free to offer any other Git workflow comments/ideas.
> ====================
> Jordan Zimmerman

*Ioannis Canellos*

Twitter: iocanel

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message