pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Alexander Lakhin <exclusion@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: gcov coverage data not full with immediate stop
Date: Tue, 12 May 2020 13:10:08 -0400
Message-ID: <28587.1589303408@sss.pgh.pa.us> (raw)
In-Reply-To: <CAH2-WzmoyiZkoxhcEKx-Cr7YQvM5fA9+iuobUrX9iqVk5sb0gQ@mail.gmail.com>
References: <20200511034243.GA5671@alvherre.pgsql>
	<28859.1589172997@sss.pgh.pa.us>
	<CA+TgmobgAFRM1+fxxga9yy1Sw7nzRu+gtE0N1DnbiaD4n0Sp1Q@mail.gmail.com>
	<29504.1589227471@sss.pgh.pa.us>
	<CAH2-WzmoyiZkoxhcEKx-Cr7YQvM5fA9+iuobUrX9iqVk5sb0gQ@mail.gmail.com>

Peter Geoghegan <pg@bowt.ie> writes:
> On Mon, May 11, 2020 at 1:04 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Yeah.  Traditionally we've waited till the start of the next commitfest
>> (which I'm assuming is July 1, for lack of an Ottawa dev meeting to decide
>> differently).  But it seems like things are slow enough that perhaps
>> we could branch earlier, like June 1, and give the committers a chance
>> to deal with some of their own stuff before starting the CF.

> The RMT discussed this question informally yesterday. The consensus is
> that we should wait and see what the early feedback from Beta 1 is
> before making a final decision. An earlier June 1 branch date is an
> idea that certainly has some merit, but we'd like to put off making a
> final decision on that for at least another week, and possibly as long
> as two weeks.

> Can that easily be accommodated?

There's no real lead time needed AFAICS: when we are ready to branch,
we can just do it.  So sure, let's wait till the end of May to decide.
If things look bad then, we could reconsider again mid-June.

			regards, tom lane





view thread (12+ messages)  latest in thread

Message-ID: <28587.1589303408@sss.pgh.pa.us>
Permalink:  ../28587.1589303408@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/28587.1589303408@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, pg@bowt.ie, robertmhaas@gmail.com, alvherre@2ndquadrant.com, exclusion@gmail.com
  Subject: Re: gcov coverage data not full with immediate stop
  In-Reply-To: <28587.1589303408@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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