----- Original Message -----
From: "Petr Schindler" <pschindl(a)redhat.com>
Cc: "Amit Saha" <asaha(a)redhat.com>
Sent: Thursday, February 28, 2013 3:58:02 AM
Subject: [Fedora Build Service] Why we are developing in develop branch?
I'd like to ask, is there any reason for developing in develop
I'm not sure what the right git work flow is, but Kamil was wondering
why we do this. My experience is that I tried master firstly and I
to develop after Tim told me about it. Wouldn't be better to develop
This is of course project specific. When I started the cleaning up of the project on
fedora hosted, I was
using the develop branch for the "cleaned up" code, or what would form the the
base for the future releases.
The master however was just a copy of the old code (from GitHub) where it was originally
started. Thus, it
was a "legacy" if you wish. My idea was that, over time, as things mature, we
would remove the master's existing contents
and move the bits from develop to master for every release. Yes, of course you could also
have release specific branches, which you
first merge from develop and then you merge the release branches into master.
So, develop -> release-x.x -> master is what I mean.
Hope it makes things clearer.
Amit Saha <http://echorand.me>
Infrastructure Engineering and Development
Red Hat, Inc.