This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
Content-Type: text/plain; charset=UTF-8
On Thu 21 Nov 2013 03:57:27 PM CET, Itamar Heim wrote:
On 11/21/2013 04:46 PM, David Caro wrote:
> On Thu 21 Nov 2013 03:03:00 PM CET, Itamar Heim wrote:
>> On 11/21/2013 03:29 PM, Ohad Basan wrote:
>>> ----- Original Message -----
>>>> From: "Ewoud Kohl van Wijngaarden"
>>>> To: infra(a)ovirt.org
>>>> Sent: Wednesday, November 20, 2013 8:27:39 PM
>>>> Subject: Puppet environment name / branch name
>>>> I just deployed r10k to be the deployment method and it works gener=
>>>> well. One problem is that it maps branches one to
one. Currently I
>>>> worked around this by making a symlink, but I think we should renam=
>>>> master branch to production. Opinions?
>> is that common? usually master is named master.
>> Infra mailing list
> Maybe it's better to change puppet config to use master as the
> 'production' environment source of manifests. I say that because it's
> usually a mess to have a branch that it's not the master as master...
> (@work we use development as master in one of the repos, and I always
> submit a patch or two a month to master instead xd)
well, one other though is that if you ever intend to have more than a s=
branch, master is usually not the stable production one...
I suppose that it depends on the flow the company/project uses, in my=20
last job we used master as the stable branch, and we had devel as the=20
non-stable branch and one branch for each major version we supported,=20
but master was always the latest major version production-ready code.=20
Then on master we had tags for each release and so on. I suppose they=20
get the idea from gitflow=20
But yes, bad habits are hard to get rid of. Any way is fine for me, but=20
if no one has any reason for the other way, I vote for using master=20
instead of production.
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
RHT Global #: 82-62605
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
-----END PGP SIGNATURE-----