public inbox for [email protected]  
help / color / mirror / Atom feed
Reminder: PG 9.1 is now EOL
3+ messages / 2 participants
[nested] [flat]

* Reminder: PG 9.1 is now EOL
@ 2016-10-25 13:02 Tom Lane <[email protected]>
  2016-10-25 19:51 ` Re: Reminder: PG 9.1 is now EOL Andrew Dunstan <[email protected]>
  0 siblings, 1 reply; 3+ messages in thread

From: Tom Lane @ 2016-10-25 13:02 UTC (permalink / raw)
  To: buildfarm-members

There's little point in continuing to test 9.1 in the buildfarm.
While we don't have reports from every active member yet on the very
last commit in that branch, the last portability-significant change
was several days ago, so I don't think there's anything more to be
learned.

			regards, tom lane


-- 
Sent via buildfarm-members mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/buildfarm-members



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Reminder: PG 9.1 is now EOL
  2016-10-25 13:02 Reminder: PG 9.1 is now EOL Tom Lane <[email protected]>
@ 2016-10-25 19:51 ` Andrew Dunstan <[email protected]>
  2016-10-29 02:47   ` Re: Reminder: PG 9.1 is now EOL Andrew Dunstan <[email protected]>
  0 siblings, 1 reply; 3+ messages in thread

From: Andrew Dunstan @ 2016-10-25 19:51 UTC (permalink / raw)
  To: Tom Lane <[email protected]>; buildfarm-members


I usually remove an EOL branch from the branches of interest file a few 
days after we've made the last release. If you're using that to get the 
branches you build it will just drop off automatically from your build 
schedule when I do that, and you don't need to do anything.

cheers

andrew


On 10/25/2016 09:02 AM, Tom Lane wrote:
> There's little point in continuing to test 9.1 in the buildfarm.
> While we don't have reports from every active member yet on the very
> last commit in that branch, the last portability-significant change
> was several days ago, so I don't think there's anything more to be
> learned.
>
> 			regards, tom lane
>
>



-- 
Sent via buildfarm-members mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/buildfarm-members



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Reminder: PG 9.1 is now EOL
  2016-10-25 13:02 Reminder: PG 9.1 is now EOL Tom Lane <[email protected]>
  2016-10-25 19:51 ` Re: Reminder: PG 9.1 is now EOL Andrew Dunstan <[email protected]>
@ 2016-10-29 02:47   ` Andrew Dunstan <[email protected]>
  0 siblings, 0 replies; 3+ messages in thread

From: Andrew Dunstan @ 2016-10-29 02:47 UTC (permalink / raw)
  To: Tom Lane <[email protected]>; buildfarm-members


This is now done.


cheers


andrew



On 10/25/2016 03:51 PM, Andrew Dunstan wrote:
>
> I usually remove an EOL branch from the branches of interest file a 
> few days after we've made the last release. If you're using that to 
> get the branches you build it will just drop off automatically from 
> your build schedule when I do that, and you don't need to do anything.
>
> cheers
>
> andrew
>
>
> On 10/25/2016 09:02 AM, Tom Lane wrote:
>> There's little point in continuing to test 9.1 in the buildfarm.
>> While we don't have reports from every active member yet on the very
>> last commit in that branch, the last portability-significant change
>> was several days ago, so I don't think there's anything more to be
>> learned.
>>
>>             regards, tom lane
>>
>>
>
>
>



-- 
Sent via buildfarm-members mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/buildfarm-members



^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2016-10-29 02:47 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2016-10-25 13:02 Reminder: PG 9.1 is now EOL Tom Lane <[email protected]>
2016-10-25 19:51 ` Andrew Dunstan <[email protected]>
2016-10-29 02:47   ` Andrew Dunstan <[email protected]>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox