Skip site navigation (1) Skip section navigation (2)

Re: marking old branches as no longer maintained

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: marking old branches as no longer maintained
Date: 2011-06-28 19:59:29
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers

On 06/28/2011 03:48 PM, Dave Page wrote:
>> But if you want to run some more frequently you'd still be stuck having to manage that yourself. There's actually not a lot of point in doing it that way, though. We don't build unless there have been changes on the branch, unless told otherwise, so you might as well run frequently and test all the branches - for the most part only HEAD (i.e. master) will be built because it gets far more changes than the back branches.
> It was something Tom asked for ages ago, so he could see if the
> Windows build got broken more promptly. I didn't want multiple
> branches running with increased frequency as I run a number of animals
> on a single machine with vmware, and a back patched change could cause
> a lot of extra work.

Oh, so maybe we need to have some sort of throttle. Probably just for 
non-head or non-(head-or-latest) would suffice.



In response to

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2011-06-28 20:07:32
Subject: Re: Fwd: Keywords in pg_hba.conf should be field-specific
Previous:From: Dave PageDate: 2011-06-28 19:48:18
Subject: Re: marking old branches as no longer maintained

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group