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

marking old branches as no longer maintained

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: marking old branches as no longer maintained
Date: 2011-06-28 17:46:22
Message-ID: 4E0A136E.6030509@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackers
I'd like to add a feature to the buildfarm that automatically picks up 
any new branch and automatically stops building any branch we're not 
maintaining any more. To do the latter, I need some way for the client 
to detect that we are or aren't interested in a branch. What I'd like to 
do is add a file to the old back branches (say from 7.4 to 8.1 currently 
- I can grandfather the rest) called "end-of-life-reached" or some such, 
with some appropriate text. As a branch reaches its end of life, i.e. 
right before the last release we make, we should add that file to the 
branch.

I think this would possibly be useful anyway, regardless of buildfarm 
utility - I still hear of people mistakenly grabbing and building 
releases past EOL, and maybe this will give one or two the extra clue 
they need that this is less than a good idea.

Comments?

cheers

andrew

Responses

pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2011-06-28 17:47:28
Subject: Re: SSI modularity questions
Previous:From: Alvaro HerreraDate: 2011-06-28 17:45:33
Subject: Re: [COMMITTERS] pgsql: Branch refs/heads/REL9_1_STABLE was removed

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