Обсуждение: upcoming infrastructure changes/OS upgrades on *.postgresql.org
-----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-----
On 2015-09-25 20:11:32 +0200, Stefan Kaltenbrunner wrote: > no date set yet though > * 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) I'm pretty sure you're already thinking of this - but let's make sure this doesn't coincide with the upcoming releases. Greetings, Andres Freund
Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes:
> * 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.
I think it's probably sufficient to run a test tarball build after
the upgrade; I can do so if you notify me when the upgrade's done.
As Andres says nearby, it would be good if this did *not* happen
during the first week of October, since we have releases scheduled
then. Actually, since that will be the final 9.0.x release, I'd
vote for postponing the borka upgrade till after that. That's
one less old branch to worry about new-toolchain compatibility for.
And if there is some subtle problem in the tarballs that we find later,
not having to reissue the last 9.0.x release would be a good thing.
regards, tom lane
On 09/25/2015 08:30 PM, Tom Lane wrote: > Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes: >> * 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. > > I think it's probably sufficient to run a test tarball build after > the upgrade; I can do so if you notify me when the upgrade's done. > > As Andres says nearby, it would be good if this did *not* happen > during the first week of October, since we have releases scheduled > then. Actually, since that will be the final 9.0.x release, I'd > vote for postponing the borka upgrade till after that. That's > one less old branch to worry about new-toolchain compatibility for. > And if there is some subtle problem in the tarballs that we find later, > not having to reissue the last 9.0.x release would be a good thing. yeah the point about 9.0.x is a very good one - so I think we will target mid/end of october for borka so we get a bit of time to deal with any fallout from the release (if needed). We could target the same timeframe for gemulon, unless people think that doing it this(!) weekend would work as well (as in would be far enough out from the upcoming releases). Stefan
Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes:
> yeah the point about 9.0.x is a very good one - so I think we will
> target mid/end of october for borka so we get a bit of time to deal with
> any fallout from the release (if needed).
Sounds like a plan.
> We could target the same timeframe for gemulon, unless people think that
> doing it this(!) weekend would work as well (as in would be far enough
> out from the upcoming releases).
Personally I would have no objection to upgrading gitmaster this weekend,
if you really wanna do it that soon. Not next weekend though, that's
too close to the release date.
regards, tom lane
On 2015-09-25 20:47:21 +0200, Stefan Kaltenbrunner wrote: > yeah the point about 9.0.x is a very good one - so I think we will > target mid/end of october for borka so we get a bit of time to deal with > any fallout from the release (if needed). > > We could target the same timeframe for gemulon, unless people think that > doing it this(!) weekend would work as well (as in would be far enough > out from the upcoming releases). Seems better to do both after the release. It's not like wheezy support is running out tomorrow. - Andres
On 09/25/2015 08:53 PM, Andres Freund wrote: > On 2015-09-25 20:47:21 +0200, Stefan Kaltenbrunner wrote: >> yeah the point about 9.0.x is a very good one - so I think we will >> target mid/end of october for borka so we get a bit of time to deal with >> any fallout from the release (if needed). >> >> We could target the same timeframe for gemulon, unless people think that >> doing it this(!) weekend would work as well (as in would be far enough >> out from the upcoming releases). > > Seems better to do both after the release. It's not like wheezy support > is running out tomorrow. yeah - Thinking about it I agree on doing both afterwards, and while wheezy still has a lot of life left we also have almost 20 boxes still left to upgrade which takes time (~40 are already done but the ones left are more complex and have more dependencies and/or complexity) so we need to keep up the pace ;) Stefan