upcoming infrastructure changes/OS upgrades on *.postgresql.org - Mailing list pgsql-hackers

From Stefan Kaltenbrunner
Subject upcoming infrastructure changes/OS upgrades on *.postgresql.org
Date
Msg-id 56058E54.40904@kaltenbrunner.cc
Whole thread Raw
Responses Re: upcoming infrastructure changes/OS upgrades on *.postgresql.org  (Andres Freund <andres@anarazel.de>)
Re: upcoming infrastructure changes/OS upgrades on *.postgresql.org  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all!

As part of our regular maintenance schedule and in our continous effort
to run our systems on current and fully supported operating systems the
postgresql sysadmin has started upgrading the OS on our infrastructure
hosts from Debian Wheezy(aka Debian 7.x) to Debian Jessie (Debian 8.x).

This mail is mostly to announce our intend to upgrade the following two
systems in the forseeable future(no date set yet though) that might
directly affect -hackers/-commiters or a subset of those (release team)
and whether people want us to take special measures ahead of time to
ensure minimal disruption to the workflow process:


* gemulon.postgresql.org - gitmaster.postgresql, master git repository
(we will likely coordinate this internally so that somebody on the team
with a commit bit will test after the upgrade)

* borka.postgresql.org - official tarball and docs build server, the
upgrade will upgrade the toolchain on that box to the respective
versions of what is in jessie. If people think it is necessarily to
(double)check the effects beforehand we would like to know so we can
coordinate some
testing.




Stefan

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJWBY5TAAoJEO1GOCPAcHIudgwQAMHCRkDy9KWWTN3gKsObwWkO
hQ+bc1CBPys5lKohI5Sv0KfunEk0DsbxzyTk3+eYmJRplzD2l8WB/dlYV7Kb0idY
Xi1CZ26/0Jc+YaQ5ImNurGEPFhhZpPw8eNJAxl6Kd7ux0ObQ8DWPKLGeZO3Jj1Mc
Ni+L8PHreg7PlE1j9MU0iSOwASCPNlS0/yf60QPHCZbCrE+7+WSsmFd0Cr8gG9oB
ClG2JzA/tylM/clsyRowAEg9NLj5l57SL/J6dlqbHZEGLy6dgGpkMhucCY8qJ87V
jgEd8jPmY9//Nvs0kIIGuvAhNty8DF0B9styXOBeNjSIbEJWaUr8VO5cRvehE8PN
KKlaFh79QvnxfnWhCWBR5LUFtFUcWBUiIyb6f7xoFY9vwS6surpxFsqiDveJyEZq
BN2z29OAtUxyRo7ZZaAwJiAoxLJ3mbZwIFIcfmXyMS/XE9SfzyuUX1uQZealRXHM
wlAR8NNmVJVOAlx6dvYawtoxJ1aAi63gjU8oQicASze+syS0vD6sKUe3BRp3vC54
st/Fv7ZEkko7Fc+2dpJKp78k+1Rz/M9YGW1XBcKqVuxUy/u6Njo90x9E0Su2cst/
0Jz/P3mckq2T/nf7AzV3Bx3TSnV5TUFPKLzm7+OwIA1lPRfsXXJ3CNRXP2hjmN1A
0Bsx1uUk1k8+bT+xhGT5
=8nHl
-----END PGP SIGNATURE-----



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Fix an O(N^2) problem in foreign key references.
Next
From: Andres Freund
Date:
Subject: Re: upcoming infrastructure changes/OS upgrades on *.postgresql.org