Re: [COMMITTERS] pgsql: Branch refs/heads/REL9_1_STABLE was removed

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Branch refs/heads/REL9_1_STABLE was removed
Date: 2011-06-28 14:39:22
Message-ID: 11497.1309271962@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> We discussed earlier to potentially block the creation, and removal,
> of branches on the origin server, to prevent mistakes like this. It
> has only happened once in almost a year, so it's probably not
> necessary - but I wanted to raise the option anyway in case people
> forgot about it.

> The downside would be that in order to create or drop a branch *when
> intended* a committer would need someone from the infrastructure team
> to temporarily switch off the branch-blocking setting, and then back
> on..

I think it would be sensible to block branch removal, as there's
basically never a scenario where we'd do that during current usage.
I'm not excited about blocking branch addition, although I worry
sooner or later somebody will accidentally push a private development
branch :-(. Is it possible to block only removal and not addition?

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Magnus Hagander 2011-06-28 14:39:37 Re: pgsql: Branch refs/heads/REL9_1_STABLE was removed
Previous Message Peter Eisentraut 2011-06-28 13:28:26 pgsql: Add composite-type attributes to information_schema.element_type

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2011-06-28 14:39:37 Re: pgsql: Branch refs/heads/REL9_1_STABLE was removed
Previous Message Alvaro Herrera 2011-06-28 14:36:13 Re: [Hackers]Backend quey plan process