Re: branches_of_interest.txt

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: branches_of_interest.txt
Date: 2018-07-01 15:41:07
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> This file on the buildfarm server is used to tell clients which branches
> we'd like built. When a new stable branch is created it's added manually
> to this file, and when one gets to EOL it's removed from the file. This
> is a rather cumbersome process, and it occurred to me that it could be
> streamlined by our keeping it in the core repo instead.

I can see the value of people other than you being able to change it,
but keeping it in the core repo seems like a kluge not a proper solution.
In particular, once it'd been around for awhile so that the master copy
had diverged from the back branches' copies, that would be pretty
confusing IMO.

Is it worth the trouble of having a separate repo for info that shouldn't
be tied to a particular PG development branch? I'm not quite sure what
else we would keep there besides this file, but perhaps other use-cases
will come up. Some of the stuff in src/tools/ has a bit of this flavor.

regards, tom lane

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2018-07-01 16:31:17 Re: Cache lookup errors with functions manipulation object addresses
Previous Message Michael Paquier 2018-07-01 14:27:19 Re: Cache lookup errors with functions manipulation object addresses