Re: [HACKERS] upcoming infrastructure changes/OS upgrades on *.postgresql.org

[Tom Lane]

Stefan Kaltenbrunner  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


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] upcoming infrastructure changes/OS upgrades on *.postgresql.org

[Stefan Kaltenbrunner]

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


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] upcoming infrastructure changes/OS upgrades on *.postgresql.org

[Andres Freund]

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


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] upcoming infrastructure changes/OS upgrades on *.postgresql.org

[Tom Lane]

Stefan Kaltenbrunner  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


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] upcoming infrastructure changes/OS upgrades on *.postgresql.org

[Andres Freund]

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


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] upcoming infrastructure changes/OS upgrades on *.postgresql.org

[Stefan Kaltenbrunner]

On 09/25/2015 08:30 PM, Tom Lane wrote:
> Stefan Kaltenbrunner  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


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers